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

What are flow details in Atlassian Automation?

When creating an automation flow, you can also select Flow details to modify various options. This page outlines the different flow details you can edit and what they mean.

Before we begin

To manage automation flows in a Jira or Confluence space, you must be an admin of that space.

To manage automation flows across a Jira or Confluence instance, you must be a Jira or Confluence app admin.

What are the flow details?

Rule details field in an automation rule

Name

What the flow is called. This is how you’ll identify your flow in the flows list or audit log.

Description

A longer description for your automation flow, in case you need more information than the name field provides.

Scope

This will impact where your flow can make changes. Scope can only be set at the Global level by a Jira or Confluence app admin.

In Jira automation, the possible scopes are:

  • Space:

    • Single space: Flow will run in a specific space.

    • Multi-space: Flow will run across several spaces of your choosing.

    • Space type: Flow will run across all spaces of a specific type (i.e. software, service, or business).

    • Global: Flow will run across all Jira spaces in that Jira instance.

  • Team:

In Confluence automation, the possible scopes are:

  • Single space: Flow will run in a specific space.

  • Multi-space: Flow will run across several spaces of your choosing.

  • Global: Flow will run across all Confluence spaces in that Confluence instance.

Allow flow trigger

If selected, your flow can be triggered by other automation flows. For example, if your flow triggers when a work item is created, then all flows that create a work item will trigger your flow.

Notify on error

Choose how often the flow owner is notified by email.

Owner

By default, this is the person who creates the flow. If a flow runs and results in an error, the owner will be notified by email.

Actor

Changes performed by your flow will be seen as being made by the flow actor.

Who can edit this flow

Choose who can manage this flow. Possible options are:

  • Private: Only the flow owner can edit the flow.

  • Specific admins: Choose one or more admins who can edit the flow.

  • All admins: All admins in the space can edit the flow, as well as all app admins.

Note that site admins will always be able to edit your flows, regardless of which option you choose.

Still need help?

The Atlassian Community is here for you.