Triggers

A trigger is a rule that reads like a sentence: When progress reaches 100% · If the type is task · Then set the status to Testing and notify whoever created it.

When, if, then

When (the event):

  • a field changes: status, status category, progress, priority, assignee;
  • a task is created; all its subtasks are closed;
  • an approval is requested or decided;
  • the due date is near, has passed, or the task has been idle for N days;
  • in a project: a project field or a question in one of its forms changes.

If (the conditions): status, category, progress, priority, assignee, type, "created by form X", fields.

Then (the actions): set status, progress, priority or a field; assign; comment; notify; send an email; request an approval.

Recipients can be: the assignee, the creator, the requester's head, the head or members of a unit, the project's Managers, a specific person.

Two levels

  • Organization: managed by whoever has the right to manage them; they apply to all projects.
  • Project: managed by the project's Manager; they apply only there.

Neither level sees the other's triggers; the owner sees everything. The plan sets how many triggers can be active at the same time in the organization; it never limits how many times they fire.

What you set is not overwritten

A trigger never changes a field that the person set in the same operation. A trigger's effects cannot be reverted with Undo: to reverse a rule, write the opposite rule.

Conflicts

Two rules that, on the same event, would write different values to the same field are a conflict, and saving is blocked. The organization can allow project Managers to exclude an organization rule from their projects; everyone involved is always notified.

Email

Trigger emails have an hourly cap per organization: beyond it, the excess emails are not sent and the owner is notified; the other actions continue.

Ready-made rules and drafts

In the editor of a new trigger you can start from ready-made rules (completed → status, overdue → high priority, idle for 7 days → reminder…). In chat you can ask the assistant for a draft: you open it in the editor and save it yourself.

Why didn't it fire?

The task's history shows what each rule did. A rule switched off by the plan limit, excluded from the project or in conflict shows this on its card on the Triggers page.

Was this page helpful?