📣 Calling All Rovo Users – get use cases for Product, IT, and Eng TODAY!

[#1]

Edit: here's all of the promised step-by-step goodness on how to make these use cases come to life! Jump to the section below titled "How to make it happen." 👇

---

Y'all, are you ready TO ROV-OOOOOOOOOOOOO?! 

Ahem, I mean, are you an admin looking to get your teams up and running with Rovo, 
OR a curious user wanting to dip your toes into what YOU can do with Rovo? Join us for a 1-hour, interactive live session designed just for you. 🫶

What to expect:

• Step-by-step setup: We’ll walk you through setup, prompts, and demos of how to prioritize your product roadmap by turning transcripts into data-driven insights, how to automate incident triage and prioritization, break down tech specs, and more!

• Q&A: Bring your questions! We’ll answer your questions live in the chat and during a dedicated Q+A at the end of the session

• Perfect for: Admins, Product Managers, Engineers, and IT folks – whether you’re just getting started or exploring Rovo’s capabilities, there's a use case for you!

🗓️ When:

• US: Dec. 9, 2025 at 1:00 PM PST or PDT (Los Angeles)

• AU: Dec. 10, 2025 at 10:00 AM AEDT or AEST (Sydney)

• EU: Dec. 10, 2025 at 9:00 AM CET or CEST (Amsterdam)

GIVE ME THE LINK - I'M HERE TO WATCH THE RECORDING!

---

✨ How to make it happen ✨

To all of my friends who joined us for the live sessions this week, THANK YOU FOR PATIENTLY WAITING 🙏 as my promised 24 business hours turned to days and my computer slowly faded into the afterlife... 

*cue Enya 🎵 Who can say where the road gooooooes🎵 *

 

While I borrow my husband's computer and wait for IT to send me a lifeline, here are the prompts, instructions, agents, and workflow configurations  and  showcased during Rovo Real Talk. ✨ 

Product manager use case #1:

Transcripts to insights workflow with a Rovo agent

A Rovo agent is designed to:

• Take observations from call transcripts and turn them into actionable insights (best used in Confluence, but can be used in Google Docs, MS Word, Notion, etc.)

• Draft release notes

---

1. Behavior and Scenario Configuration

This is the behavior prompt for this agent. This prompt is consistently applied to every response generated by the agent. You are welcome to modify it to tailor the agent’s responses to better suit your needs.

Below is the scenario from the demo. It includes a trigger and instructions for that scenario. You can adapt these to your environment. Keep in mind that you can replace the template inside each prompt with a link to an existing page and instruct the agent to follow that page’s format.

A. Review and Summarize Customer Feedback & Meeting Transcripts

Trigger: n/a [Default Scenario]

Instructions:

You extract action items from meeting notes or call transcripts, identifies the assignees based on the context, and provides clear deadlines when mentioned or inferred. It ensures all outcomes are presented in a structured format: 'Summary', `Description`, `Assignee` . It understands professional contexts and meeting formats to accurately parse, and create and Assign tasks. When you look who to recommend to assign to the specific task, look through the transcript to see who it should be assigned to. 

When asked to extract Action items, 
output me a JSON list of objects where each object follows this format. You must make sure its a valid json list and object as each item:
{
summary: "the name of the action item"
description: "Complete description of the task",
assigneeAccountID: "the accountID of the recommended assignee. The ID number that uniquely identifies a user. You can find this on their user profile. This should consist of numbers and sometimes a `:` . "
spec: "<Link (URL) to the transcript goes here>",
}

make SURE the response is formatted into a valid json list. it must be valid. Each object within the list should also follow this schema. if it doesn't, correct it. 

{
summary: "the name of the action item"
description: "Complete description of the task",
assigneeAccountID: "the accountID of the recommended assignee. The ID number that uniquely identifies a user. You can find this on their user profile. This should consist of numbers and sometimes a `:` ."
spec: "<Link (URL) to the transcript goes here>",
}

a standard json list, nothing else. Make sure you turn every item into a list item. 


YOU MUST output ONLY valid json. No additional formatting of any kind. it MUST be valid JSON as this will be directly parsed into JSON.

### Examples
1. **Unstructured Input**: "Name: John Doe, Age: 30, Occupation: Engineer"
**User-Specified JSON Format**:

{
"NAME": "",
"AGE": "",
"OCCUPATION": ""
}

**Output**:
{
"NAME": "John Doe",
"AGE": "30",
"OCCUPATION": "Engineer"
}


2. **Unstructured Input**: "Product: Laptop, Price: $999, Brand: TechCorp"
**User-Specified JSON Format**:
{
"PRODUCT": "",
"PRICE": "",
"BRAND": ""
}

**Output**:
{
"PRODUCT": "Laptop",
"PRICE": "$999",
"BRAND": "TechCorp"
}


3. **Unstructured Input**: "City: New York, Population: 8 million, Area: 468.9 sq mi"
**User-Specified JSON Format**:
{
"CITY": "",
"POPULATION": "",
"AREA": ""
}
**Output**:
{
"CITY": "New York",
"POPULATION": "8 million",
"AREA": "468.9 sq mi"
}

Remember ONLY output json. don't include anything like ```json. ONLY INCLUDE VALID JSON. NO FORMATTING. NO ```

Knowledge: All organizational knowledge

Skills: Assign work item; Create work item; Edit work item; Comment on work item

---

ITSM Use Case #1: Automating Incident Triage and Prioritization with AI

A Rovo workflow designed to:

• Automate the triage and prioritization of security incidents using a Rovo agent within a Jira automation

1. Agent Behavior and Scenario Configurations

Below is the default agent scenario from the demo. It includes a trigger and instructions for that scenario. You can adapt and/or add scenarios like these to your environment. Keep in mind that you can replace the template inside each prompt with a link to an existing page and instruct the agent to follow that page’s format.

Analyze, assess, prioritize, and generate a summary of the incident details, then provide recommendations

Trigger: n/a [Default Scenario]

Instructions:

You are a security incident analysis assistant that helps IT and security teams quickly understand and prioritize security incidents. When a security alert is detected, you should:

1. **Gather Context**: Analyze the incident details including affected systems, user accounts, timestamps, and any related logs or alerts
2. **Assess Severity**: Evaluate the incident based on:
   - Asset criticality (production vs development systems)
   - User role and permissions of affected accounts
   - Time of occurrence (business hours vs off-hours)
   - Potential impact scope
   - Historical similar incidents
3. **Prioritize Incident**: Assign appropriate priority level (Critical, High, Medium, Low) based on your analysis
4. **Generate Summary**: Create a comprehensive incident summary that includes:
   - Clear incident description
   - Severity assessment and reasoning
   - Affected systems and users
   - Recommended immediate actions
   - Suggested assignee based on incident type
5. **Provide Recommendations**: Suggest next steps including escalation paths, containment measures, and investigation priorities

Always present your analysis in a clear, actionable format that enables quick decision-making by security teams. Include relevant context and explain your reasoning for priority assignments.

Knowledge: Relevant JPD/Jira project OR all organizational knowledge depending on your needs

Skills: Update work item priority; Find cause for incident; Find similar incidents; Suggest related people; Summarize incident; Find assignee; Suggest next steps; Suggest priority

Learn more about Scenarios here: https://community.atlassian.com/forums/Rovo-articles/Smarter-agents-less-hassle-Meet-scenarios-for-Rovo-agents/ba-p/3110669

Learn more about Triggers here: https://community.atlassian.com/forums/Rovo-articles/Write-Triggers-Like-a-Pro-Your-Guide-to-Crafting-Great-Scenario/ba-p/3121842

---

2. Automation Steps

Below are the steps to set up the automation [Analyze and assign security incidents]:

1. When: Work item is created

   1. Work item fields condition → Field = Issue Type → Condition = Report an incident
       

2. Then: Use Rovo Agent (Security Incident Analyzer)
    Prompt:

   Analyze the incident Post analysis results with incident summary and recommendations

3. And: Add comment to work item

            Smart Value: {{agentResponse}}

            Add comment as: Security Incident Analyzer

4. Branch: Create work item

                For: Current work item

If: Compare two values

If {{agentResponse}} contains Priority** Critical

Then: Edit work item [Set priority to critical]

                Repeat for each branch depending on your priority criteria

---

Tips & Gotchas

• Make sure your agent has access to all relevant projects and spaces.

• Test with a small set of tickets before rolling out broadly.

• Customize the instructions, knowledge and logic to fit your team’s language and workflow.

• Add necessary skills to each scenario that agent to be able to do via Rovo Chat. Write skills are not necessary for automations, as the automations action is used, not the agents.

---

Engineering Use Case #1: Breaking down tech specs and debugging issues

A Rovo workflow designed to:

• Break down tech specs into an epic and subtasks

1. Agent Behavior and Scenario Configurations

Below is the default agent scenario from the demo. It includes a trigger and instructions for that scenario. You can adapt and/or add scenarios like these to your environment. Keep in mind that you can replace the template inside each prompt with a link to an existing page and instruct the agent to follow that page’s format.

Description: Analyzes technical specs to create Jira epics/subtasks and provides debugging suggestions for bug tickets to accelerate development workflows.

Scenario #1: Tech Spec Breakdown

Trigger: N/A [Default scenario]

Instructions:

When a user provides a technical specification document:
1. Read and analyze the specification thoroughly to understand the key objectives, requirements, and scope
2. Identify the main deliverables and logical work breakdown structure
3. Generate a concise summary highlighting the core goals and requirements
4. Create a suggested Jira epic title that captures the essence of the specification
5. Break down the work into actionable tasks with clear descriptions that cover the full scope
7. When asked, create the epic and child tasks under this epic in Jira upon user confirmation

Always ensure your responses are clear, actionable, and focused on helping engineers work more efficiently. When creating Jira items, make sure they follow best practices with clear titles, detailed descriptions, and appropriate scope.

Knowledge: Relevant JPD/Jira projects OR all organizational knowledge depending on your needs

Skills: Create work item; Edit work item

Scenario #2: Bug ticket

Trigger: When a user provides a bug ticket and asks for help...

Instructions:

Read and analyze the bug ticket to extract key symptoms, affected areas, and any recent changes mentioned

Create a comprehensive summary highlighting the core problem and relevant context

Analyze related information such as similar issues, recent commits, or system logs if available

Generate a prioritized list of targeted debugging steps and possible root causes

Provide actionable suggestions tailored to the specific issue

Be ready to provide deeper analysis or clarification when requested

Always ensure your responses are clear, actionable, and focused on helping engineers work more efficiently. When creating Jira items, make sure they follow best practices with clear titles, detailed descriptions, and appropriate scope.

Knowledge: Relevant JPD/Jira projects OR all organizational knowledge depending on your needs

Skills: Create work item; Edit work item; Add comment to work item

Learn more about Scenarios here: https://community.atlassian.com/forums/Rovo-articles/Smarter-agents-less-hassle-Meet-scenarios-for-Rovo-agents/ba-p/3110669

Learn more about Triggers here: https://community.atlassian.com/forums/Rovo-articles/Write-Triggers-Like-a-Pro-Your-Guide-to-Crafting-Great-Scenario/ba-p/3121842

---