The plugin ships two assignment-related triggers. One watches a task's single assignee. The other watches a project's multi-person assignee roster. Keeping them conceptually together makes it easier to choose the correct one for your automation.

Assignment triggers are useful when the important change is not the work item's state, but who is now responsible for it. Use them when you want to notify a new assignee, log a reassignment, detect that a project has lost its last owner, or kick off a follow-up workflow when ownership changes.

Task Assignment Changed

The Task Assignment Changed trigger is the simpler of the two because a task has only one assignee at a time. This makes it a good fit for straightforward handoff automations such as welcoming somebody to a new task, alerting a team when ownership was removed, or recording when work was reassigned from one person to another.

Its Change Type setting lets you choose whether you care about a first assignment, an unassignment, a reassignment, or any of those changes. Like the task lifecycle trigger, it also offers a Parent Project Type filter so you can keep the automation focused on tasks under the kinds of projects that matter to that process.

Task Merge Fields

• Entity is the task whose assignee changed.
• ChangeType is the specific transition that occurred: Assigned, Unassigned, or Reassigned.
• AssignedToPersonAlias is the task's current assignee. It is empty when the task was unassigned.
• PreviousAssignedToPersonAlias is the previous assignee. It is empty when the task was assigned for the first time.
• Project is the task's parent project.
• ProjectType is the parent project's type.

Project Assignment Changed

The Project Assignment Changed trigger is for cases where the whole assignee roster matters. Because projects can have multiple assignees, the interesting question is often not just "who is assigned now" but "did the team gain people, lose people, or end up with nobody responsible?" This trigger is a good fit for ownership and coverage automations.

Its Change Type setting lets you watch for assignees being added, removed, or changed in any direction. The two extra checkboxes are what make it especially useful: Initial Assignment Only helps when you care about a project getting its first owner, while Final Unassignment Only helps when you need to detect that a project has become orphaned.

Unlike the task trigger, this one can summarize a whole edit. If several people are added or removed in one save, the trigger still fires only once for that save, which keeps downstream automations from becoming noisy.

Project Merge Fields

• Entity is the project whose assignee roster changed.
• PreviousAssigneeCount is the number of assignees before the save.
• CurrentAssigneeCount is the number of assignees after the save.
• AddedAssigneeAliases is the list of PersonAlias records added during that save.
• RemovedAssigneeAliases is the list of PersonAlias records removed during that save.
• ProjectType is the project's type.