Rovo Agents in automations

Project or global admins can use Agents in automation rules to reduce time spent on more complicated repetitive tasks. Using an Agent within an automation rule allows you to generate and share content in any product integrated with Atlassian Automation.

How to use an Agent in Automation:

  1. From Project settings or Global settings, select Automation.

    1. In a team-managed project, select Service project settingsAutomation.

  2. Select Create rule in the top-right corner.

  3. Select a trigger for the rule. This will specify when you want the Agent to act based on a trigger (For example, a Jira issue changing status).

  4. Configure the trigger settings and select Next.

  5. Select New component to add a New action.

  6. From the list of actions, select Use Rovo Agent.

    1. Give the Agent a prompt to follow when triggered (For example, read and review the quality of the description field for {{issue.url}}). The Agent will respond to this prompt in the background each time the rule is triggered. Use Smart Values in your prompt to reference objects like Jira issues or Confluence pages.
      More about Smart Values in Jira
      More about Smart Values in Confluence

  7. Choose what to do with the Agent’s response using the {{agent.response}} smart value. You can do this by adding additional actions or components that require free text and putting {{agent.response}} in the free text field. When you add this additional action or component, you can also choose the author of the content (For example, you could add a comment to an issue and choose for it to appear as the rule creator, or as the Agent). Whatever you configure will happen automatically whenever the rule is triggered and won’t require additional confirmation from users.

  8. Finish configuring the rule.
    More on creating and editing automation rules in Jira

For now, only a few actions in the rule builder allow you to use the Agent response. We’ll continue to add more and more actions that integrate with Agents.

Even if you choose to appear as the author of the Agent's response in an automation rule, the product will show a note to indicate this content was created by an Agent through automation.

Examples of Agents in automation rules

Scenario

Rule

Using the Decision Director, create an automation rule that is triggered by any new Confluence pages with the word “DACI” in the title to leave a comment with a review of the document and suggested improvements including resources to inform the decision.

  1. When: Page published

  2. If: AI condition

    1. Content in title is related to DACI

  3. Then: Use Rovo Agent

    1. “Review the content on {{page.url}} and give recommendations”

  4. Then: Add comment

    1. {{agent.response}} as Decision Director

Using the Jira issue organizer, create an automation rule that is triggered every time an issue is created without a parent (or epic) to leave a comment on the new issue with a suggested epic from that project that could be a relevant parent issue.

  1. When: Issue create

  2. If: Issue fields conditions

    1. type

    2. is one of

    3. [all child issue types]

  3. And: Related issue condition

    1. Parent

    2. Does not exist

  4. Use Rovo Agent

    1. Find a relevant parent (or epic) for {{issue.url}} and explain why you recommend it.

  5. Then: Add comment to issue

    1. {{agent.response}}

Using the Jira Theme Analyzer, create an automation rule that sends a Slack summary of customer feedback captured in the past 2 days based on a JQL search that captures the relevant data in a Jira project.

  1. When: Scheduled

    1. Every 2 days at 8:00am

  2. Then: Use Rovo Agent

    1. Identify themes from these issues [insert JQL search]

  3. And: Send Slack message

    1. {{agent.response}}

 

Still need help?

The Atlassian Community is here for you.