Skip to main content

Bulk update Assignment Triggers after a team change

Replace assignees or subscribers across one Checklist, review the proposed changes and test future task routing.

Written by Logan Bowlby

Overview

When responsibility for inspection faults moves to another team, update the Assignment Triggers that create the work. The Checklist editor can replace selected trigger settings across every page in that Checklist.

At a glance

Who can do this

Super Users, Checklists › Modify, or authorized Checklist folder Editors.

Where

Checklists › editor › Bulk change

Works on

Backend (web), Mobile app

Availability

All organizations

💡 Why this matters: Reviewing the complete change list helps prevent one overlooked question from continuing to send work to the previous team.


Before you start

This is a replacement operation across the Checklist, not a find-and-replace for one named person. If different questions must keep different receiving teams, edit those triggers individually. Confirm the new User Group is assignable and has the required Location access; see assignee eligibility.


Walkthrough

1. Open Bulk change

Open the intended Checklist and select Bulk change. Start with one Checklist whose triggers should share the same new ownership. Keep a PDF backup before a wide change; see Checklist maintenance.

2. Choose the settings to replace

Tick the change for Assignment Trigger assignees and select the replacement team. Change subscribers separately if the people following the work also change. Leave the Assignment Definition change unticked unless changing the workflow is intentional. Selected empty lists can remove existing selections.

3. Review the proposed changes

Select Apply to open the change list. Check the Page, Question, new assignees and struck-through previous values. Cancel if the list includes questions that should keep their existing routing. Applying this list updates the open Checklist editor.

4. Save and inspect an affected trigger

Save the Checklist, then inspect representative triggers. In particular, check Assign to user that answered the question: bulk-changing the fixed assignee list does not turn that option off. Confirm the effective routing, title, Definition and automatic-creation setting.


Check the outcome

Complete one controlled test inspection as a representative User and check who receives its new Assignment. Existing Assignments keep their current assignees; use bulk Assignment management to transfer those separately. Saving the Checklist applies the change to every Schedule using it.


Best practices

  • Use a stable User Group for ongoing ownership.

  • Change one routing concern at a time.

  • Include both automatic and manually confirmed triggers in the test.


Frequently asked questions

Does changing subscribers also change the assignee?

No. Subscribers follow work; assignees own it. Select the two changes separately. Notifications still follow each User’s notification settings.

Will this move Assignments already created?

No. It changes the Checklist’s trigger settings for future work. Reassign existing tasks separately.

Why is the new group not selectable?

Check its Assignability settings, the Assignment Definition’s assignee restrictions and Location access. See assignee eligibility.

Did this answer your question?