From Confluence page to backlog, in four steps
Spec2Tickets does the mechanical work of breaking a Confluence page into structured Jira issues — you stay in control and approve everything before it lands. Here's the whole flow.
The workflow
Install & configure
Add Spec2Tickets from the Atlassian Marketplace. After installing, it opens as a page inside Confluence — open its in-app Settings from there (no digging through Atlassian's admin) to paste your Anthropic API key and a default Jira project key. About five minutes — no servers, no infrastructure.
Generate
Pick a Confluence page and click Generate. Claude reads the whole page and produces a structured breakdown — typically in a few minutes (longer for large pages, or when Anthropic is under heavy load). You can leave and come back; it keeps running.
Review in the editor
Every breakdown opens in an interactive editor. Adjust feature names, user stories, acceptance criteria, dependencies, priority, story points, and labels inline. Quality signals — confidence, risks, ambiguities, and any circular dependencies the app auto-resolved — are surfaced so you know where to look.
Push to Jira
When it looks right, click Push to Jira. Spec2Tickets creates one Epic, a Story per feature, the subtasks beneath them, and the “blocks / is blocked by” links between features — all under your own Atlassian permissions, with links back to the new issues.
What lands in Jira
A breakdown isn't just a list of titles. Each one arrives enriched and ready to work.
A full hierarchy
One Epic for the page, a Story per feature, and Subtasks beneath each Story — structured the way your team already plans.
Descriptions & acceptance criteria
Stories and subtasks come with a user story, acceptance criteria, and a description — so developers start from a definition of done, not a guess.
Sizing signals
Each Story comes with a suggested priority, story-point estimate, and complexity signal — editable before you push.
Dependency links
Cross-feature “blocks / is blocked by” relationships are detected and created as real Jira links, so sequencing is visible from day one.
Quality signals
The review screen flags low-confidence features, risks, and ambiguities — and shows any circular dependencies the app resolved for you.
Labels & categories
Features are grouped and labelled by category, and you can add or edit labels on the Epic and every Story before pushing.
Nothing reaches Jira until you push it — every breakdown runs under your own Anthropic key, so your content stays under your own Anthropic agreement.
Ready to try it on a real Confluence page?
Install from the Marketplace and turn your next page into a reviewed, sprint-ready backlog.
Free up to 10 users · Bring your own Anthropic API key · Runs on Atlassian Forge.