Developers Spend 16% of Their Time Coding

▶ Watch (01:07)

Atlassian’s 2025 developer experience report found that 99% of surveyed developers say AI tools save them time. But those same developers spend only 16% of their workday writing code. The other 84% goes to reading tickets, chasing requirements, switching tools, and reviewing work. That is where the real friction lives.

“99% of developers that responded to this report report that they’re saving time using AI tools” — Jovana Dunisijevic

Rovo Dev is built to work on that 84%.

What Rovo Dev Does in the CLI

▶ Watch (03:58)

Three demos in the CLI show the range. First: pass a Jira ticket link, Rovo Dev reads the requirements and updates the site’s avatars. Second: paste an annotated screenshot with problem areas circled, Rovo Dev reads the image and fixes the date, location, and logo. Third: assign a ticket to build a memory card game with a dedicated tab, and Rovo Dev ships the full feature.

She walked through the Rovo Dev CLI demo: ticket, screenshot, and memory game (03:58) live.

Bringing Jira Context into GitHub Copilot

▶ Watch (07:18)

The Atlassian MCP Server for GitHub Copilot adds Jira and Confluence context directly inside VS Code. Install takes one script from the Atlassian docs. After that, Copilot can pull a Jira issue by ID alone, read its description and requirements, and generate implementation code without tab-switching. The demo also shows Copilot answering an org-specific question about Atlassian’s feature flag rollout process, pulling the answer from Confluence. The integration is free for Jira and Confluence users who already run GitHub Copilot.

AI Code Review That Checks Against Requirements

▶ Watch (10:29)

Rovo Dev’s code reviewer runs automatically after every pull request on enabled repos. It comments on the diff with findings on bugs, readability, and maintainability. Acceptance criteria checks go further: the reviewer compares what was built against the requirements in the originating Jira ticket, so missed requirements surface before merge. Custom instructions let teams teach the reviewer their own standards. Describe the rules in natural language, commit that file, and the reviewer enforces them.

“generic code review bots often miss the mark” — Jovana Dunisijevic

Notable Quotes

99% of developers that responded to this report report that they’re saving time using AI tools Jovana Dunisijevic · ▶ 1:08

16% of their time is actually going into coding Jovana Dunisijevic · ▶ 1:25

generic code review bots often miss the mark Jovana Dunisijevic · ▶ 11:50

Key Takeaways

  • Developers spend only 16% of their time writing code; Rovo Dev targets the other 84% of non-coding work.
  • The Atlassian MCP Server pipes Jira and Confluence data directly into GitHub Copilot inside VS Code.
  • Rovo Dev’s code reviewer checks pull requests against original Jira ticket requirements, not just code style.