From automating ticket readiness checks to understanding usage credits, we’ve captured the most frequently asked questions from this month’s sessions.
🎥 Watch session replay
📚 Explore more use cases
Can Rovo track sprint scope changes and show velocity impact?
Answer: Yes. You can create a Rovo Agent that compares sprint scope across dates or statuses, calculates added/removed work, and comments on the velocity impact using Confluence or Jira data sources. This can be automated using JQL and Rovo Actions.
Are the agents shown in the class already available?
Answer: Yes, we've shown you out-of-the-box (or Atlassian created for you) agents included with Rovo.
I don’t see all out-of-the-box agents. How can I access them?
Answer: If you don’t see specific agents like “Readiness Checker” or “Release Notes Drafter,” try checking permissions or open a support ticket. You may not have Rovo in your environment yet.
Can we flag issues that fail readiness and rework them?
Answer: Yes. You can use a Rovo Agent to tag or comment on issues that don’t meet defined criteria. Then query or automate their improvement individually or in bulk.
Can we chain Rovo Agents so one feeds into the next?
Answer: Yes. Atlassian is developing a feature called Scenarios, which lets you sequence agents to complete multi-step processes. Until then, chaining via automation or passing responses between agents is possible with custom development.
Do Rovo Agents require coding?
Answer: Out-of-the-box (or Atlassian made for you) agents do NOT require coding to use, copy or customize. However, creating custom actions or advanced automation scenarios does require coding via Forge CLI.
Can Rovo link Jira user stories to Confluence pages?
Answer: Yes. Rovo can retrieve related Jira issues and link or display them on Confluence pages. This can be automated through an agent or set up manually.
Do Rovo Agents consume credits for every chat message?
Answer: No. Credits are counted per new agent interaction or prompt execution, not per keystroke. Follow-up messages or automation triggers may also incur usage depending on the action taken.
What LLMs does Rovo use?
Answer: Rovo uses a combination of over a dozen large language models. Model selection is based on the job you're trying to do, and handled automatically by Atlassian’s orchestration layer.
Can we choose which model to use?
Answer: Not at this time. Model selection is handled internally based on your task, prompt, and context.
Does the model train on our data?
Answer: No. Rovo does not use your data to train the LLMs. Your data stays within your environment and is used only to generate responses for your prompts.
Is Rovo access or billing tied to all users or just those who use it?
Answer: Usage-based billing models reflect actual use. You won’t be charged for users who don’t interact with Rovo once billing begins. Current access is included with your subscriptions without limits.
Will non-licensed or portal-only JSM users be able to access Rovo?
Answer: This is under active development consideration. Consider upvoting the feature request and keep an eye out on the roadmap.
Is there a way to email Confluence reports automatically with Rovo?
Answer: Yes—with automation rules or Forge. You can schedule JQL triggers and have an agent generate a report and email it using templates
Can we restrict who can edit or manage specific Rovo Agents?
Answer: Permissions management for agents is being developed. Expect more granular controls to be released soon.
Dr Valeri Colon _Connect Centric_
Strategic Growth Leader
Connect Centric
Washington, DC
45 accepted answers
0 comments