Rovo Dev is Atlassian's answer to the question: what does a coding agent look like when it has full access to the business context around every ticket? While other agents work from code repositories alone, Rovo Dev connects to Atlassian's Teamwork Graph — a knowledge layer mapping Jira work items, Confluence documentation, Bitbucket code history, and team goals — giving it the context of why code needs to change, not just what needs changing.
Key capabilities
Jira-native workflow — Developers can start a Rovo Dev session directly from a Jira work item. The agent converts the ticket's acceptance criteria, linked docs, and project context into an implementation spec and works toward a merge-ready PR, with the Jira ticket as the ground truth for what done looks like.
PR review against acceptance criteria — Code reviews cross-reference the Jira acceptance criteria for the change being reviewed — validating that the implementation actually satisfies the stated business requirement, not just that it compiles and passes linters.
Teamwork Graph context — Access to Confluence documentation means Rovo Dev can read architecture decision records, API documentation, and runbooks when making implementation choices. The agent understands the system the code runs in, not just the code itself.
Adaptive memory — The CLI retains project-specific knowledge across sessions, accumulating understanding of the codebase and team conventions over time.
Autonomy level
Level 4 — Near-autonomous. The agent accepts a Jira issue, autonomously researches the codebase and relevant documentation, implements the change, and opens a PR. Human review and merge approval is required; the agent does not self-merge.
Strengths
- Deepest Jira/Confluence/Bitbucket integration available — unique for Atlassian shops
- #1 on SWE-bench Full leaderboard at 41.98% (November 2025)
- 30.8% reduction in PR cycle time in Atlassian's own peer-reviewed study (ICSE'26)
- 5M+ monthly active users on the Rovo platform overall
- $20/developer/month with CLI, IDE, and web interfaces
Limitations
- Maximum value only for teams using Jira and Confluence; less differentiated for non-Atlassian stacks
- Requires Atlassian Cloud Premium or Enterprise plan as prerequisite
- Claude-only model; no model choice
- Proprietary and closed-source; no self-hosting