Skip to content
Help center

Automations

Every rule on the projects you can open, in one place: rules that act on a project's tasks so people do not have to chase, with how often they have run and what they did.

Make a rule

  1. Press New rule.
  2. Choose the project under Which project is it for? and press Continue.
  3. Give it a Name, and choose under When what sets it off: a task added, given to somebody, moved to done, due soon or overdue.
  4. Press Add condition to narrow it, up to 5 conditions that must all hold: its priority, who it is given to, its column, a milestone, when it is due.
  5. Choose what it does, up to 5 things: tell people, give the task to somebody, add a task, or change its priority, column or due day.
  6. Press Save and turn on.

Then: It runs from the next task it finds. A notice it sends is one of the app's own lines with the task's title; a rule never writes a message of its own, and it tells only people who can open the task. The person whose change set it off is not told what they did.

Rather not? Open Templates and press Use this on one, choosing the project, to start from a rule already written.

Sokha wants the owners of the Warehouse move project told when anything is finished. Sokha makes a rule: when a task moves to done, notify the project's owners. Each owner who can open the project is told "Task done" with the task's title; whoever marked it done is not.

Try a rule on a task first

  1. Press the rule's name in the list.
  2. Under Test this rule, choose one of the project's tasks.
  3. Press Run on a sample task.

Then: It says whether the rule would act on that task, what each condition found, and what each action would do and who would be told. Nothing is sent and nothing changes.

See what a rule has done

  1. Read the line under each rule: how often it acted in the last 30 days, and when it last did.
  2. Open Run history for every time a rule acted, could not do something, or was skipped for the month's or a night's limit, and why.

Then: A task's own Activity says what an automation changed on it. A rule whose conditions did not hold writes nothing in the history: try it on the task with Test this rule.

If rules are skipped for the month

  1. Read the card at the top: how many times your organization's rules have acted this month, against what your plan allows.
  2. Remember that one project may use at most 40% of the month, so the rest always have the other 60%.
  3. Wait for the date the card names, or ask your Owner about a plan that allows more.

Turn a rule off, change it or delete it

  1. Press the switch beside the rule to turn it off, and again to turn it on.
  2. To change it, press its name, change what it does, and press Save.
  3. To remove it, press its name and then Delete rule.

You see the rules of every project you can open, and change those of the projects you run. Automations are part of Tasks & projects, so they go when it is switched off or not in your plan.

Automations · ORG-APP