Skip to main content

Avoid duplicate Assignments

When you raise an Assignment, Mobaro shows existing ones that match the same Definition and target, so you don't open a duplicate.

Written by Logan Bowlby

When you raise an Assignment, Mobaro looks for Assignments that already exist for the same work and lists them, so you can act on the open task instead of opening a second one for the same issue.

You'll need to be a Super User or have Assignments: Create, with access to the target Location, to raise Assignments.


How duplicate detection works

As you fill in a new Assignment, Mobaro compares it against existing Assignments and surfaces any that look like the same task. It matches on three things:

  • Assignment Definition — the type of Assignment

  • Target — the Location or Asset

  • Title — the Assignment's name

When there's a match, open the existing Assignment and add to it (a comment, a status change, another assignee) instead of creating a duplicate.


The same-Definition limitation

Detection only compares Assignments that share the same Assignment Definition. Two Assignments describing the same real-world issue under different Definitions, or one default Assignment and one Definition-based Assignment, are never matched as duplicates of each other.

Note: Matching is also scoped to the same target. The same fault logged on two different Locations or Assets isn't flagged, because they're treated as separate work.

Best practice: Standardize which Assignment Definition a given kind of work uses, so repeat reports of the same issue line up under one Definition where detection can catch them. If the same fault can be raised under two Definitions, you'll get parallel Assignments the check can't connect.


Frequently asked questions

Does Mobaro stop me from creating a duplicate?

No. It surfaces existing matches so you can decide. If the work is genuinely separate, you can still create the new Assignment.

What does it match on?

The Assignment Definition, the target Location or Asset, and the title.

Why didn't it catch an obvious duplicate?

The two Assignments most likely use different Assignment Definitions, or sit on different targets. Detection only compares Assignments of the same Definition on the same target.

Can I detect duplicates across different Definitions?

No. Consolidate by standardizing the Definition used for that kind of work, so matches fall within a single Definition.

Did this answer your question?