Overview
When a task moves between teams, keep the same Assignment if it remains the same piece of work. Change the assignee and record the handover so the new team can see the original fault and progress.
At a glance |
|
Who can do this | Users allowed to modify the Assignment and delegate to the receiving team; Assignment Definitions may impose further limits. |
Where | Assignments › open Assignment |
Works on | Backend (web), Mobile app |
Availability | All organizations |
💡 Why this matters: One continuing record makes it easier to distinguish a handover from a second, duplicate repair request.
Before you start
Agree who is accepting the work and confirm the receiving group is assignable at the Assignment’s Location. Check the current Definition’s restrictions and the receiving team’s rights to progress or resolve it.
Walkthrough
1. Record the handover context
Open the Assignment’s Activities and write what has been done, what remains and any restrictions. Mention the receiving team if they need a notification. A comment or mention alone does not change the assignee.
2. Change the responsible team
Edit the Assignment and change Assigned to to the agreed User or User Group. Preserve the Location and Asset when the work still belongs to the same equipment. Save the change.
3. Review the deadline and workflow
Check the current priority, dates and Definition state. Reassignment is not a reason to mark unfinished work as Finished. If your Definition hides or fixes a date field, follow its policy instead of expecting an unrestricted deadline editor.
4. Confirm the handover record
Inspect the activity feed and current assignee, then have the receiving team confirm they can open and progress the task. Use your normal operational handover channel for urgent work; do not rely solely on a notification.
Check the outcome
Previous assignees can remain subscribers after reassignment. Unsubscribe turns off a person’s notifications but is not an access-removal control. If the change is part of a staff departure, review account and Location access separately. See Assignment followers and delegable User Groups.
Best practices
Keep the original Assignment when it is the same work.
State the next action and owner explicitly.
Check receipt before the outgoing team leaves.
Frequently asked questions
Why can’t I select the receiving group?
Check Assignability, your delegation rights, Location access and the Definition’s assignee rules. See assignee eligibility.
Will the old assignee stop following the task?
Not automatically. Former assignees remain subscribers. Their notification preferences and Location access still matter.
Does mentioning a team transfer responsibility?
No. A mention can subscribe and notify them. Change Assigned to to transfer the task itself.