Automating Jira Ticket Creation from Daily Meeting Summaries with Rovo

[Mariska]

We hold daily Zoom call meetings, and summaries of these meetings are generated using NotebookLM. I import these summaries into Confluence, organizing them into a specific folder. I am now working on creating a Rovo agent that can analyze these summaries and, when necessary, automatically create Jira tickets based on the action items or discussions outlined in the notes.

However, I can only create chat agents in Rovo so far, and I’m unsure if I need Atlassian Intelligence in addition to the Rovo subscription to achieve this functionality.

[Jensen Fleming]

HI @MariskaWhat a great use case. Currently Rovo Agents in chat can only perform one action at a time, however we are working on bulk actions right now. 

However, you can accomplish this using Rovo Agents and Confluence Automations. I've made a loom here to walk you through it: https://www.loom.com/share/7cf41d602121457ab94411c68f12164f?sid=3519b1b1-1ebf-4cfa-8eab-4bb9579ddc0a

This will allow you to do this automatically without having to prompt the Agent in Chat. Keep in mind you can change the Automation trigger to be whatever you like. 

There are other Rovo demos in that loom folder as well, to help inspire some ideas: https://loom.com/share/folder/67587304fadd44c3914fcd7a08c36be0

Let me know if you have any questions!

Jensen

---

In addition here is a link to the Agent's Instructions I showed in the demo: 

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 ```