Create rules 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 rules.
The quality, accuracy, and reliability of rules created with AI may vary. Learn why
How do I use Rovo to create a rule?
Rules are automated workflows constructed in an “if this happens, then that happens” format. Admins can create and enable rules that function across Jira at the space or app level.
You can use Rovo to generate rules by simply describing the rule you want to create. To get started:
Go to Space settings and select Automation.
Click on the input box beneath Create rules quickly with Rovo to begin typing.
Describe the rule you’d like to create, including a trigger and action. You can use one of the examples provided or write your own rule.
Select Preview rule to see a preview of the rule that was generated.
Check the summary of the rule generated by Rovo, and add any missing steps or details.
Once you’re happy with your rule’s configuration, select Enable rule.
Your rule will now be enabled and visible in the rule library.
What’s required to create a rule?
Each rule 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 rule. To successfully create a rule with Rovo, your rule must at least contain a trigger and an action.
Triggers
A trigger is what causes a rule to run. Your rule 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 rule to do. It will execute when a rule 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 rule. You may still need to configure individual steps or add more details to your rule before it can be enabled. You can also add conditions or branches to your rule 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 rule 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 rule must be compatible with Jira automation. With the exception of the trigger and actions mentioned above, Rovo can support any of the components in the following list:
View available automation steps in Jira
What errors can occur when using Rovo to create a rule?
When using Rovo to create rules 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 rule creation requests, and can’t create your rule as a result. Wait a few minutes and then try creating your rule 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 rule. Wait a few minutes and then try creating your rule again. |
An unknown error occurred | We’ve encountered an error that prevented us from creating your rule, but we aren’t sure what caused it. Wait a few minutes and then try creating your rule again. |
We’re unable to create your rule | We tried to create your rule, however for an unspecified reason, we couldn’t finish creating it. This may be due to your requested rule not being specific enough, or containing language our system couldn’t understand. Try creating your rule 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 rule with it. Try creating your rule 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 rule with it. Try creating your rule again, making sure to remove any malicious content from your prompt. |
If errors persist or you'd like additional support, contact us here.
Was this helpful?