Jira & Confluence

Bring in issues, sprints and pages, or send this project's stories and docs out, and keep both in step.

Connect

Connectors → Jira & Confluence → Sign in with Atlassian, and approve access.
Or, if your company prefers tokens: or use an API token. Create one at id.atlassian.com → Security → API tokens → Create API token with scopes, choose Atlassian MCP V2 with all scopes, and paste it with your Atlassian email. Your Atlassian admin must allow API tokens for the Rovo MCP server.
Optional: set the default Jira project and Confluence space so Releavo knows where stories and docs go.

Releavo looks at your recent activity (issues you viewed, projects you lead, spaces you write in) and recommends one of:

Bring it in: this project is new and a Jira project already holds the work.
Send this project there: this project has docs and stories and Jira doesn't.
Link the two: both have the same work; it matches them up instead of copying.

Pick an answer from the buttons in chat. After that it keeps them in step in the background.

Stories become issues with the story key in the summary and a releavo label; docs become Confluence pages.
Releavo never deletes or closes issues it didn't create unless someone asks.
Status from Jira shows up on the backlog and the roadmap; sprints and releases come across too.