The plan used to have to be re-typed at the keyboard. A senior engineer described a ticket in a 600-word spec, a team triaged it in a 20-minute meeting, and then someone re-keyed the rough shape into the editor before any code existed. Atlassian's new AI suite for Jira collapses that handoff into one loop: ticket → spec → pull request, with the agent doing the re-keying. That's a real win, and it deserves to be called out before anything else.
[[DIAGRAM: Jira work item assigned to a coding agent (Claude Code, Cursor, or Copilot) → agent picks up ticket and opens a PR through the built-in Jira Coding Agent → Jira Planner pulls Jira + Confluence history to draft a spec in Confluence → @Jira in Slack files a work item from a thread → state syncs back into Jira for review and triage]]
Atlassian shipped four pieces in one wave, and they fit together cleanly. Each one is worth understanding on its own.
The four pieces, and what each one actually does
Coding-agent handoff. Jira work items can now be assigned directly to Claude Code, Cursor, or GitHub Copilot. OpenAI's Codex integration is on the roadmap. The ticket becomes the prompt; the agent becomes the assignee. No copy-paste between the issue tracker and the editor.
