Use Cases for Rovo within Automation Rules?

[Shahpur Khan]

Hi all! I'm excitedly investigating Rovo's capabilities for my team of web developers, project managers and QA. I feel that there is huge potential for timesave and cost-cutting thanks to Rovo's ability to be integrated into Automation Rules. I want to try creating some useful Automation Rules using Rovo, but I'm having trouble thinking of (or finding) specific ideas that both fit within Rovo's current abilities and serve a noticeable benefit in Jira (or, by extension, Confluence).

So, in what ways are you all using Rovo (either default Rovo or custom Agents) in Automation Rules for your teams? All inspiration is appreciated.

[Liz Tanner]

Hey there, Shahpur! We had a Rovo training-heavy week where I thought of two Rovo Agent use cases for both Jira and Confluence. In my two user cases, I used Out-of-the-box agents, Global Translator and Blocker Checker for my examples:

-Global Translator: Translates all of your written content, including in Confluence, into other languages. The first use case could be for an org who is looking to reach new audiences in global audiences. Another could be when a Project Lead fluent in one language needs to translate a LOT of project documents like meeting notes, apps & system documentation, how to access their org's 2FA, and other documents to their  outsourced animation team.

Full transparency: The 2nd example is real! I speak only English. The animation team we hired spoke only Russian.  Global Translator would've saved at least 2 weeks of extra work. (~80 hours of labor!)

-Blocker Checker: This Agent is designed specifically to be used within automation rules involving Jira issues. The Agent analyzes keywords in the issue indicating the issue could be blocked. The Agent signals the automation rule to change the issue status to blocked. The use case I instantly thought of was combining Blocker Checker with another automation rule to prevent or rapidly resolve a blocked issue. When Blocker Checker changes a Jira issue status to blocked, I could include another automation rule in the workflow like this one that Slack messages the issue owner of the now-blocked status. This notifies our issue owner in (nearly) real time to review the issue and remove any impediments to progress if Blocker Checker was accurate.

As I said, we had an awesome training set this week in Rovo as well by Dr. Valeri Colón with so many more brilliant use cases and examples. I will send her webinar and other links in a follow-up message. I hope this first bit of info helps get your ideas going!

[Benedikt Dollinger]

That sounds really interesting, @Liz Tanner  - thanks for sharing this.

[Shahpur Khan]

Thank you Liz -- sorry for the delayed reply. These are awesome insights and resources, especially the ACE event videos! Great work on your agents and automation rules.

[Liz Tanner]

Rovo Documentation and ACE Events really sparked my interest in Rovo and inspired my Agent outlines and designs. The Support Docs I really liked for use cases are here: 

• Atlassian site: Rovo 'Features' page detailing 8 Out-of-Box and 8 Custom Agents--
• Add'l Custom Agents on Marketplace--excellent source for cost-effective, pre-built Agents w/ descriptions that can serve as user case ideas
• Rovo Product Guide: Shows a multi-departmental use case w/ Jira Theme Analyzer.
• 3rd party app Connectors + Actions +  Automation rules--user cases here too!

Dr. Valeri Colón and the Connect Centric team's ACE Events are by far the best sources for ideas, though. I left the 2nd to immediately outline a few Forge Rovo Agent ideas. Both here:

• Part 1: Transform Your Workflow with Atlassian Intelligence & Rovo
• Part 2: Rovo Essentials: Use, Customize, Create

I hope these inspire you and your team to create awesome Jira/Confluence solutions too!