Rules

Rules allow you to streamline routine tasks and establish workflows with ease. For a rule to work, you need a trigger that activates the rule and an action that is performed automatically. For example, a rule can be created to automatically assign a task (action) when a due date is set (trigger).

Power up your processes with Asana Rules. Join our Creating basic workflows in Asana virtual training to learn how. Register now.

Rule usage

Visit our dedicated article for a detailed overview of rule usage.

Creating a rule

There are two ways to create a rule for your project. Either select an automation from the rules gallery in your project, or create your own custom rule. The custom rule builder is available on Asana Starter, Advanced, Enterprise, and Enterprise+ tiers, as well as legacy tiers Business, and Legacy Enterprise.

To create a rule from the gallery:

1. Navigate to Customize in the top-right corner of your project
2. Click + Add rule
3. Select a rule from the gallery
4. From the drop-down select Runs on tasks or Runs on tasks and subtasks
5. Click on the three dot icon to add additional settings
6. Fill out the specified parameters
7. Click Create rule
   
   

To create a custom rule:

1. Navigate to Customize in the top-right corner of your project
2. Click + Add rule
3. Select Create custom rule
4. From the drop-down select Runs on tasks or Runs on tasks and subtasks
5. Click on the three dot icon to add additional settings
6. Choose a name for your rule
7. Choose triggers and actions
8. When you have selected your desired options, click Create rule.`

Rules will only run on the first level of subtasks (i.e. rules will not run on sub-sub-tasks, sub-sub-sub tasks, etc.)

Editing a rule

Edit your rules any time by navigating back to the project and selecting the rule you want to update.

You can edit a rule by clicking the pencil icon next to the rule on your sidebar.

Any edits you make to your rules will only apply to a project's tasks and content on a go-forward basis. Edits will not apply retroactively.

Pausing a rule

You can pause a rule at any time by clicking the pencil icon next to the rule on your sidebar.

Deleting a rule

You can delete a rule at any time by clicking the pencil icon next to the rule from your sidebar, and then clicking the Delete button.

Section-based rules

On paid plans, the rules lightning bolt icon will appear in sections (on list and board view) that have rules. Once the rule triggers, the icon will become animated. Clicking the icon will open a rules menu for that section, allowing users to add new rules or edit existing ones.

You can edit a rule by clicking the pencil icon that appears when you hover over it.

Trigger combinations and multiple actions

Custom rules with conditions, the Approval status changed trigger, and the Add comment action are available on Asana Starter, Advanced, Enterprise, and Enterprise+ tiers, as well as legacy tiers Business, and Legacy Enterprise.

You can also use trigger combinations and/or conditional logic and multiple actions to automate routine tasks so your team doesn’t have to think about them.

You can use the acton performed by one rule to trigger another.

Additional triggers and actions

Using other trigger and actions:

1. When the status of an approval changes, you can specify the action that happens as a result
2. Create a comment that will post as Asana anytime a selected trigger happens
   
   

Trigger: Due date approaching

Customers on Asana Starter, Advanced, Enterprise, and Enterprise+ tiers, as well as legacy tiers Business, and Legacy Enterprise can create a custom rule in the rules dialogue and find Due date is approaching in the list of triggers. You can choose from a couple of preset options or click Custom for more options.

The Custom option allows you to specify how many minutes, hours, days, or weeks before the due date the rule should trigger.

Trigger: Task overdue

Customers on Asana Starter, Advanced, Enterprise, and Enterprise+ tiers, as well as legacy tiers Business and Legacy Enterprise can find the Task is Overdue trigger when creating a custom rule. You can choose from a few preset options or click Custom for more options.

With the Custom option, you can specify the number of minutes, hours, days, or weeks after the task becomes overdue for the rule to trigger.

If you choose days or weeks when setting up your trigger, it will ignore due times and fire based on due dates only. However, if you choose minutes or hours, it will respect due times.

Additional notes on due date approaching and task overdue triggers

• These triggers fire based on the moment a task becomes due or overdue, not simply because a task is due or overdue.
• Both of these triggers will not retroactively fire upon rule creation for all of the existing tasks in the project that match their criteria. They will only fire for due events that happen after rule creation.
• These triggers only fire for incomplete tasks.
• Rules with day or week precision will not execute precisely at midnight. Rather, these rules will execute in the window between 00:00 and 01:00.

Action: Create task

With an Asana Starter, Advanced, Enterprise, or Enterprise+ subscription, or a subscription on legacy tiers Business or Legacy Enterprise, you can use rules to create tasks, milestones, and approvals in your project automatically. Choose a trigger or combination of triggers, and Asana will create the task when the rule runs. You can pre-select the task name, assignee, relative due date, and more.

To create a task with a rule:

1. Navigate to Customize in the top-right corner of your project
2. Click + Add rule, then Create custom rule
3. Choose a trigger or combination of triggers
4. When the trigger is selected, click the Actions tab
5. Under Create new, select Task

Action: Create subtask

Customers on Asana Starter, Advanced, Enterprise, and Enterprise+ tiers, as well as legacy tiers Business and Legacy Enterprise can create a custom rule in the rules dialogue and find Subtasks in the list of actions.

Subtasks allow you to add a predefined list of subtasks to a task automatically.

To add a subtask:

1. Click on Subtasks.
2. Write the name of the subtask.
   
   

As soon as one subtask is added, the rule can be created.

You can create up to 20 subtasks.

To edit the rule, click on the pencil icon next to the rule on your sidebar. The changes made will be automatically saved.

Action: Remove task from project

Previously you could use rules to add tasks to a project. You can now also remove tasks from projects using the Remove task from project action, unlocking more options to automate actions in your projects. 

To use the Remove task from project action:

1. Navigate to Customize in the top-right corner of your project
2. Click + Add rule, then Create custom rule
3. Choose a trigger or combination of triggers
4. When the trigger is selected, click the Actions tab
5. Select Remove task from the project, under the Move task section
   
   

Action: Set task title and description

You can now use a rule to set a task title and description. These rule actions can be found in the Actions tab of the rule builder under the Change task field to… section.

Action: Set task title to

To set a task title:

1. Navigate to the Actions tab of the rule builder
2. Choose Set task title to
3. Enter the task title in the box provided under Task Name
4. Click Create rule

The example in the screenshot above uses the trigger Task is added to this project. In this case, any tasks added to the project will be automatically given the title you provided under Task Name when creating the rule.

Action: Set task description to

To set a task description:

1. Navigate to the Actions tab of the rule builder
2. Choose Set task description to
3. Enter the task description in the box provided under Description
4. Click Create rule

The example in the screenshot above uses the trigger Task is added to this project. In this case, any tasks added to the project will be automatically given the description you provided under Description when creating the rule.

Note: The description provided when building this rule will replace any existing task description when the rule runs.

Adding variables when setting a task title or description

The Set task title and description feature also supports dynamic values meaning that you can have the task title or description refer to a specific variable like a task, person, date or custom field. For example: "New work needed from [Assignee]".

Including variables in your task title

1. Choose Set task title to as your rule action.
2. Click the + icon to the right of the text field.
3. Choose from the variables Task, People, Dates or Custom fields.

Including variables in your task description

1. Choose Set task description to as your rule action.
2. Click into the text field and then click the + icon in the lower left-hand corner.
3. Select Variable and choose from the variables Task, People, Dates or Custom fields.

Updating text and numerical custom fields

You can also use rules to update the contents of a text custom field or a numeric custom field. This means that you can select the values for a text custom field or numeric custom field based on a previous trigger.

Text custom field: 

When the trigger of task moved to a section is set to To Be Scheduled, you can add the action of setting the Content Channel custom field to “Blog”.

Numeric custom field:

When the trigger of Content Stage(QGEC) is set to On Hold, you can set the action to select the estimated time.

Rule types

The maximum number of rules per project is set at 50, regardless of plan size or tier.

Custom rules

Triggers

• You can add up to 20 triggers per custom rule
• You can select the trigger more than once
• You cannot choose the Due date is approaching or Task is overdue triggers for subtasks. To use either of these triggers you must change the rule to Runs on tasks.

Multiple actions

• When one or more triggers happen, you can select up to 5 actions to occur as a result.
• You can't add the same action more than once.

Column or section based triggers

Column or section based triggers are for Boards View projects or projects that have been updated to use the new, collapsible sections.

Custom field rules

Custom field rules are available on all projects with custom fields. People custom fields are also supported.

To unlock these rules, you must first add a custom field to your project.

Triggering rules

You can trigger a rule from anywhere (web, mobile, external integrations). If you update something on a task, we check to see if that task is in any projects with rules, and if your action is the trigger on any of those rules.

Projects you don't have access to

You can trigger rules on projects that you don’t have access to, but the yellow lightning bolt icon will not be displayed to indicate that a rule is running.

Anyone can trigger a rule, including Guests.

Permissions: a few considerations

Rules, much like custom fields, are now editable by other members of the project by default. Rules that multi-home tasks into other projects are also now visible from the customize menu. These rules can be paused directly from their project.

• You now have the option to allow others with edit access the ability to edit rules. Now rules that are created will default to editable.
• Only the owner of a rule can delete a rule.
• When updating rules on projects and templates, the editor must have the correct permissions to save all of the rules. For example, if the rule adds tasks to another project, then the editor must also have edit permissions in that other project.
• When a rule is duplicated via project duplication, the duplicating user becomes the owner with insufficient privileges. In this instance, the rule is disabled, but the owner still has editing access.
• Rules are designed to keep running even when the owner's access control permissions change. For example, if a rule is set up to add tasks to a project and you later lose access to that project, the rule will continue to run.
• When a rule is copied or duplicated via project templates (new and legacy versions), the template user will become the rule owner. Here, the rule will only be disabled if the template duplicator has insufficient access control permissions for the rule. For example, you cannot edit a project to which the rule wants to add tasks.
• If a user leaves a project, the rule will not break. However, if there are no other users interacting with the project the rule will be disabled.

Who can enable or disable a rule?

Any user with edit access to a project in which a rule is running will be able to enable or disable a rule created by someone else.

Users with edit access are also the only ones that can view the change history.

A user with edit access can pause or activate a rule but only the owner can edit a rule's triggers and actions.

The rule owner is still the only person that can edit or delete a rule.

Deprovisioning

When you deprovision someone who has rules, their rule will be paused and ownership of any rules on projects will be passed to the project owner.

If there is no project owner, ownership will be passed to the admin who deprovisioned the user. Only the new owner of a rule can re-activate the rule to have it continue running.

When a rule owner is deactivated and the new owner has sufficient permissions, this means that the rule will continue to run which the new owner will then be able to edit.

Updates on misconfigured rules

If a rule becomes mis-configured (example: “Marked complete > Move to column “Done” and someone deletes your “Done” column), we will email the owner of the rule to let them know to fix it.

• We will email you the first time a rule is triggered but cannot fire due to being misconfigured. We will not email you again until it has been corrected and successfully run at least once before misconfiguring again.

• All users with read access to the rule in question can see the correct status of the rule.

• Once you update the rule to a correct configuration and save the updates, those warnings will go away.

Rules integrations

Rules are an important part of many workflows, and so are integrations with third party services (e.g., Slack). Now, you can use a rule to integrate your team's favorite tools into your work in Asana, and let rules do the heavy lifting automatically. You can set specific triggers in your Asana projects, and trust rules to automate your workflow when your chosen criteria are met.

For example, the Slack + Asana rule integration allows you to send a message to a teammate in Slack, triggered by task or project completion.

You can create a rule which pings a specific channel in Microsoft Teams based on criteria such as a change in a custom field value.

Or create new issues in Jira Cloud and Jira Server when a task is added to a particular project section.

Recently launched rules integrations also support actions within Gmail, PagerDuty and Twilio. Learn more about configuring their respective rule integrations here.

Rules using integrations require proper app management settings and user authentication with the third party services.

Triggering actions within apps

There are three types of triggers for rules, and this is also true for triggering actions with rules integrations.

Task added type triggers

• Task added to a section
• Task added to this project

Task updated type trigger

• Based on approval status
• Based on completion status
• Based on assignee
• Based on due date
• Based on attachments added
• Based on comments added

Task timing type trigger

• Task is no longer blocked
• Due date is approaching
• Task is overdue

Forms

When tasks are created from forms they can trigger any of the following triggers:

Task added to a project

This trigger will apply to all tasks being added to a project, not just from forms.

Custom field set

For each drop-down custom field in the project, you will see a trigger and an action. So if your project has "Priority" and "Stage" custom fields, you'll see "Priority set" and "Stage set" as triggers. You pick which value on that custom field you want to trigger a rule.

Example: If you have a drop-down custom field on your form for Type of Request, with the options “Blog” and “Website”, you can set a rule on the project for “When ‘Type of Request’ is set to ‘Blog’ it will add that task to the ‘Blog requests’ project.”

This only works for drop-down custom fields on the project. Some form's drop-downs are not custom fields.

Form submission triggers

With form submission triggers, you can automatically move your forms to a new process without having to triage them manually. Form submission triggers can help you standardize your intake process and automate forms in your workflows.

To set your form submission trigger:

1. From the Triggers tab, click on To a project
2. Choose Form submissions as a source
3. Choose a form
4. Choose an action

After setting the trigger, you’ll be able to see your rule in the customize menu.

Every time a form is submitted, you will receive a notification. You can also keep track of the form submission’s history through the task details pane.

Guest permissions

Guests cannot create or own rules, but they can trigger rules.

Pricing

Rules are available across every paid tier in Asana. The custom rule builder is available on Asana Starter, Advanced, Enterprise, and Enterprise+ tiers, as well as legacy tiers Business and Legacy Enterprise.

A subset of rules are available to customers on the legacy tier Premium:

• Move to column/section > Mark complete
• Mark complete > Move to column/section
• Custom field changed > Move to column/section
• Move to column/section > Set custom field
• Custom field changed > Mark complete
• Mark complete > Set custom field

Inverse actions for rules

Inverse actions are available on Asana Starter, Advanced, Enterprise, and Enterprise+ tiers, as well as legacy tiers Business and Legacy Enterprise

Inverse actions are a compliment to existing rules that now provide the option to reset or remove data. By providing the option of inverse actions for rules, we have created a more robust rule engine that better maps the structure, quality and efficiency of customer workflows.

Available inverse actions:

• Unassign task
• Move task to another project
• Clear due date
• Mark task incomplete
• Remove collaborators

Inverse action capabilities support the reassignment, resetting or movement of tasks from one project to another.

Variables in rules

Variables allow you to create dynamic, flexible rules to fit your workflow. See our dedicated article on variables in rules for more.