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 is a flow actor?

Any changes performed by an automation flow are seen as being performed by the flow actor. When configuring a flow, space admins, app admins, and site admins have the option to change the flow actor to someone else.

In Confluence automation, the flow actor is the person who created the flow.

In Jira automation, the default flow actor is the “user” called Automation for Jira. For example, if an automation flow transitions a work item to Done, that work item’s History tab will show as having been transitioned by Automation for Jira.

Issue history in Jira, showing the issue's status was set to Done by a user called "Automation for Jira"

Changing the flow actor

Anyone with permission to edit a flow can change the flow actor.

  • In Confluence automation, you can set the flow actor as yourself, but can’t change it to someone else.

  • In Jira automation, you can set the flow actor as yourself, or as the Automation for Jira user. App administrators can set anyone as the flow actor.

To learn more about changing a flow's actor, see Run Jira flows as another user (Jira only).

 

Still need help?

The Atlassian Community is here for you.