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

Create flows with Rovo in Jira automation

AI and Rovo aren’t available for Jira in an Atlassian Government environment.

Rovo is a virtual teammate to help you and your team to work more effectively. Using AI and machine learning, Rovo is integrated into our cloud-based apps. In Jira automation, you can use Rovo to quickly and easily create automated flows.

The quality, accuracy, and reliability of flows created with AI may vary. Learn why

How do I use Rovo to create a flow?

Flows are automated workflows constructed in an “if this happens, then that happens” format. Admins can create and enable flows that function across Jira at the space or app level.

You can use Rovo to generate flows by simply describing the flow you want to create. To get started:

  1. Go to Space settings and select Automation.

  2. Click on the input box beneath Create flows quickly with Rovo to begin typing.

  3. Describe the flow you’d like to create, including a trigger and action. You can use one of the examples provided or write your own flow.

  4. Select Preview flow to see a preview of the flow that was generated.

  5. Check the summary of the flow generated by Rovo, and add any missing steps or details.

  6. Once you’re happy with your flow’s configuration, select Enable flow.

  7. Your flow will now be enabled and visible in the flow library.

What’s required to create a flow?

Each flow is made by selecting a triggering event, and adding different types of steps: actions, conditions, and branches. Think of each step as a building block of a flow. To successfully create a flow with Rovo, your flow must at least contain a trigger and an action.

Triggers

A trigger is what causes a flow to run. Your flow must contain one trigger. Triggers can listen for events, such as a page being created in your space, or be scheduled to run on a certain time or date. In the following examples, triggers are highlighted in bold:

  • When a work item’s status is changed to DONE, then transition all linked work items to DONE.

  • Every 7 days, create a new work item with title "Feature Flag Review".

  • When a bug is created, then set the due date in 7 days, and then email the ticket owner.

Actions

An action is what you want your flow to do. It will execute when a flow runs successfully. Examples of actions in Jira automation can include creating a new work item or sending an email. In the following examples, actions are highlighted in bold:

  • When a work item’s status is changed to DONE, then transition all linked work items to DONE.

  • Every 7 days, create a new work item with title "Feature Flag Review".

  • When a bug is created, then set the due date in 7 days, and then email the ticket owner.

Keep in mind that one trigger plus one action are the minimum steps required to successfully create a flow. You may still need to configure individual steps or add more details to your flow before it can be enabled. You can also add conditions or branches to your flow if you’d like to make it more detailed.

What steps are supported by Rovo?

Rovo doesn’t support the following trigger and actions:

  • Incoming webhook trigger

  • Send web request action

  • Delete work item action

For a flow to be successfully created, all its steps must be supported by automation in Jira. This means that any triggers, actions, conditions or branches in your flow must be compatible with Jira automation. With the exception of the trigger and actions mentioned above, Rovo can support any of the steps in the following list:

View available automation steps in Jira

What errors can occur when using Rovo to create a flow?

When using Rovo to create flows in automation, it’s possible to encounter some errors. The following table provides more information about errors that can occur:

Error Type

Additional Information on Error

The volume of requests in system is too high

Rovo is currently processing a high volume of flow creation requests, and can’t create your flow as a result. Wait a few minutes and then try creating your flow again.

We’re unable to connect to server

Due to a connection error, we’re currently unable to connect to the server and create your flow. Wait a few minutes and then try creating your flow again.

An unknown error occurred

We’ve encountered an error that prevented us from creating your flow, but we aren’t sure what caused it. Wait a few minutes and then try creating your flow again.

We’re unable to create your flow

We tried to create your flow, however for an unspecified reason, we couldn’t finish creating it. This may be due to your requested flow not being specific enough, or containing language our system couldn’t understand. Try creating your flow again by entering a more specific prompt.

Prompt was too long

Your prompt exceeded our word limit of 300 words, meaning we aren’t able to create a flow with it. Try creating your flow again by shortening your prompt.

We’re unable to use the prompt

Your prompt may have contained malicious or unethical content, meaning we aren’t able to create a flow with it. Try creating your flow again, making sure to remove any malicious content from your prompt.

If errors persist or you'd like additional support, contact us here.



Still need help?

The Atlassian Community is here for you.