Overview
Resolving an Assignment is more than flipping it to Finished — it's where the record of what was done gets captured. This article explains how to resolve an Assignment on the Backend, when documentation is required, how reopening works, and why the activity feed matters as an audit trail.
Users must be Super Users or meet the following to change an Assignment's state:
Be directly (as a User) or indirectly (through a User Group) assigned to the Assignment, and
Have the Assignments: Modify permission, with access to the Assignment's Location
Why this matters: A resolved Assignment with a clear Solution tells the next person what happened and why. Documentation is also what clears a Critical for operation task and returns a Location or Asset to Ready for operation.
What happens when you resolve
Reaching a finished or final state changes more than the label.
Concept | What it means |
Solution | A description of how the task was completed, optionally with comments and photo attachments for the record. |
Required documentation | A state in an Assignment Definition can require documentation before it can be entered, forcing a Solution or note at resolution. |
Critical for operation | Resolving (or lowering the priority of) a Critical for operation Assignment is what returns the Location or Asset to Ready for operation. |
Activity feed | Every state change, comment, and edit is logged with the User and timestamp — a complete audit trail. |
Resolving an Assignment on the Backend
1. Open the Assignment
In the Mobaro Backend, go to Assignments and open the Assignment you want to resolve.
2. Move it to a finished state
Change the status to Finished (or the relevant final state if the Assignment uses an Assignment Definition).
3. Add the Solution and any documentation
Record a Solution describing how the task was completed, and add comments or photo attachments. If the state requires documentation, you'll be prompted before it can be saved.
4. Save
Click Save. The resolution and all documentation are written to the activity feed.
Note: Assignees can also resolve on the go. See How to close and resolve an assignment on mobile and How to change the state of an assignment on mobile.
Reopening a resolved Assignment
If work needs to continue after an Assignment was finished, you can reopen it.
1. Open the resolved Assignment and choose Reopen
From the Assignment, select the option to reopen it.
2. Provide a justification
Enter a reason for reopening. This is recorded on the activity feed so the history stays clear.
Note: When you reopen an Assignment, you're set as the assignee. Reassign it afterward if someone else should own the continued work.
Example: closing out a repair
Scenario
A High priority Assignment marked Critical for operation was raised on a water slide after a cracked panel was found, taking the slide out of operation.
Setup
The technician replaces the panel and opens the Assignment in the mobile app.
They move it to Finished, write a Solution, and attach an after photo.
Result
The slide returns to Ready for operation, and the activity feed shows who resolved it, when, and how — available for any later audit.
Frequently asked questions
Q: Why won't Mobaro let me finish an Assignment?
A: The Assignment's workflow may require documentation before its final state, or you may not be assigned or hold the Modify permission. Add the required Solution, or check your access.
Q: Does resolving an Assignment delete it?
A: No. Finished Assignments remain in the system with their full history for reporting and auditing.
Q: Can I reopen an Assignment that someone else finished?
A: Yes, with the right permissions. You'll be asked for a justification and will become the assignee on reopen.
Q: Where can I see who changed what?
A: The activity feed on each Assignment logs every status change, comment, reassignment, and edit with the User and timestamp.