Thanks to everyone who joined our Generate and improve content with Rovo session.
We explored practical ways to use Rovo to get started faster, improve work you have already drafted, and uncover useful information across Jira, Confluence, and connected tools.
Rovo works best when you tell it what you want to create or improve, who the audience is, which pages, work items, files, or links it should use, and the structure or tone you need.
You do not need to write the perfect prompt the first time. Start with a clear outcome, review the response, then ask Rovo to refine it.
For example:
Create a six-slide leadership update using this project plan. Start with the outcome, show progress and risks, include the next three decisions needed, and keep the tone concise and professional.
We looked at using Rovo to create and improve draft pages, live docs, whiteboards, databases, Confluence Slides, and Jira work item descriptions.
Create with Rovo gives you a starting point that you can review, adjust, and refine before adding it to Confluence.
Useful resources:
Rovo is equally useful when you already have a rough draft. Ask it to remove repetition, rewrite for a non-technical audience, check clarity and tone, identify missing information, or apply your team’s expected format.
Always review the output before you publish or share it. Rovo can accelerate drafting and editing. You still make the final decision.
Rovo can help you define unfamiliar terms, summarise long pages and Loom recordings, identify themes in Jira work items, and research a topic across connected knowledge.
Use Chat for quick questions, rewriting, and summaries.
Use Think deeper for more structured analysis.
Use Deep research when you need a detailed, cited report.
The more specific your context and question, the more focused the result.
A standard GitHub for Jira integration links development work to a Jira work item when the Jira key appears in the branch name, commit message, or pull request title.
For example, a developer might create branch APP-123-add-notifications. Jira can then show the related branch, commits, and pull request in the work item’s Development panel.
When your organization has connected GitHub to the Teamwork Graph, Rovo can use eligible GitHub context alongside Jira work and Confluence documentation.
Useful resources:
Code Context is an open-beta capability for GitHub users. It helps Rovo Chat and AI coding agents search and reason across relevant code, Jira work items, documentation, and other connected context.
An organization admin must enable Code Context and configure the GitHub for Atlassian connector. It also respects existing source-control permissions.
Learn more:
Want to build your Rovo skills further? Explore the Atlassian Community Learning calendar to find upcoming free classes, live learning sessions, and opportunities to learn alongside other Atlassian users.
What is one piece of work you would like Rovo to help you create, improve, or understand?
Share the context, your intended outcome, and where you are stuck in the comments. That will make it easier for the Community to help.
Emma Wolstencroft
2 comments