Fresh terminology for automation rules and components

An automation ‘rule’ is now a ‘flow', and a ‘component’ is now a 'step’. You may notice some inconsistencies in the documentation while we make this change. Read more about the updates in Automation

Permissions required to manage automation flows

Space automation

By default, all space admins can create and manage automation flows for their spaces. To be a space admin, they’ll need the following permission:

Stop space admins from creating and managing automation flows for their space

Global admins can disable the ability for space admins to create and manage flows. However, system flows will still be created when a space is created. Read more about system flows

  1. Select Settings (), then System.

  2. Select Global automation.

  3. Select More actions (), then Global configuration.

  4. Use the dropdown to choose specific users and groups, or uncheck Allow space administrators to manage space flows to remove the ability for space admins to create and manage flows for their spaces.

Global automation

Anyone who has the Administer Jira global permission can create and manage automation flows across all of Jira. Learn more about global permissions in Jira Cloud.

Admins with the Administer Jira global permission can:

  • Create and manage automation flows with any scope. This means they can create single-space flows, multi-space flows, or flows that affect all spaces.

  • View Jira-wide automation data, such as number of executions used.

Team automations

Once Operations are enabled for their teams, all Operations admins can create and manage automation flows. Read more about Operations.

Operations admins are different from team admins. Anyone with the user role Admin in a team’s Operations is an operations admin. Read more about member roles in operations.

To create and manage automations in Operations:

  1. Go to your team, and select Go to operations from your team detail.

  2. Select Automation in the sidebar.

  3. Create a flow from the flow builder.

Recurring work automations

By default, any user with view and edit permissions can create recurring work automations within a space. How to set up a recurring work item

These automations allow for a specific work item to be cloned automatically based on a schedule.

Executions of these automations count towards edition usage limits. How is my usage calculated?

Stop non-admins from creating and managing recurring work automation flows

Global admins can turn off the ability for non-admins to create and manage recurring work flows.

  1. Selec Settings (), then select System.

  2. Select Global automation.

  3. Select More actions (), then select Global configuration.

  4. Uncheck Allow non-admins to create recurring flows

Existing recurring work automations will need to be manually deleted.

Still need help?

The Atlassian Community is here for you.