Documentation

Setup & usage guide for Spec2Tickets

Two names, one product — the app is published on the Atlassian Marketplace as Spec2Tickets. Spec2JIRA is the vendor name and this site's domain. They are the same product.

Overview

Spec2Tickets turns a Confluence page into a structured Jira breakdown — one Epic, Stories, Subtasks, cross-feature dependency links, and quality signals — using Anthropic's Claude Sonnet 4.6.

It runs entirely on Atlassian Forge. There is no server to host, no GPU, and no Docker. The app uses your own Anthropic API key (Bring Your Own Key), so AI processing happens under your own Anthropic account.

Requirements

Atlassian	A Confluence Cloud + Jira Cloud site, with admin rights to install and configure an app.
Anthropic API key	An API key from console.anthropic.com with billing/credits enabled. Cost is typically a few cents per breakdown, billed to your Anthropic account.

That's it — no infrastructure, drivers, or downloads.

Step 1 — Install from the Atlassian Marketplace

Install Spec2Tickets for Confluence and Jira from the Atlassian Marketplace into your site. It installs into Confluence and connects to Jira, so you'll approve it for both products.

You use Spec2Tickets entirely in Confluence; Jira is simply where the issues are created. There is no separate app screen on Jira — if you set the app up from Jira and went looking for it there, you won't find a screen to open. The Jira connection just lets the app create the Epic, Stories, and Subtasks in your Jira project. Everything you do — picking a page, generating, reviewing, and pushing — happens on the Confluence side.

Seeing two entries in Manage Apps is expected. Because Spec2Tickets works across both Confluence and Jira, it registers once for each product — that's normal for a cross-product app, and the permissions it requests explain why.

Where to open the app in Confluence

There are two ways to open Spec2Tickets, both in Confluence:

From the top navigation: in Confluence, go to Apps → Spec2Tickets. This opens the app, where you pick the page you want to convert.
From a page: on any Confluence page, click the ••• (more actions) button at the top right and choose “Generate Breakdown with Spec2Tickets” — this opens the app with that page already selected.

Step 2 — Get an Anthropic API key

Go to console.anthropic.com and sign in (or create an account).
Open Settings → API Keys → Create Key and copy the key (it looks like sk-ant-api03-…).
Make sure your Anthropic account has billing or credits set up under Billing.

Not technical? Follow the plain-English, step-by-step walkthrough — no background needed — at Get your Anthropic API key (it covers the easy-to-miss billing step too).

Your key stays yours. Spec2Tickets stores it in Atlassian's encrypted Forge secret storage and uses it only to call Anthropic on your behalf — see Data & privacy.

Step 3 — Configure the app

Open Spec2Tickets in Confluence (Apps → Spec2Tickets, or the ••• → “Generate Breakdown with Spec2Tickets” action on a page — see Where to open the app). The first time, click Settings (top-right of the app) to open its configuration screen.
Paste your Anthropic API key.
Set a default Jira project key (e.g. SCRUM) — the project where issues will be created — then Test & Save.
(Optional) If your Jira project requires custom fields on create, add them under Advanced.

Step 4 — Generate a breakdown

Open Spec2Tickets in Confluence (see Where to open the app) and pick the Confluence page you want to convert. If you opened it from a page via the ••• action, that page is already selected.
Click Generate AI Breakdown. Claude analyzes the page and produces the breakdown — typically a few minutes (longer for large pages or under heavy Anthropic load). You can leave the page and reconnect later; generation keeps running.

Step 5 — Review & edit

Review the breakdown before anything is written to Jira. You can edit:

Feature names, user stories, descriptions, and acceptance criteria.
Priority, story points (suggested), and a complexity signal per Story.
Labels on the Epic and on each Story.
Shared (cross-cutting) acceptance criteria — assign them to the right Story.

The review screen also surfaces quality signals — confidence per feature, risks, ambiguities, and any circular dependencies it auto-resolved.

Step 6 — Push to Jira

Click Push to Jira. Spec2Tickets creates, in your project:

One Epic for the page.
A Story per feature (with priority, story points, and labels).
Subtasks under each Story.
“blocks / is blocked by” links for cross-feature dependencies.

Issues are created with your own Atlassian permissions — you'll see links to the new Epic and Stories when it's done.

Pricing

Plan	Price	Breakdowns
Free trial	$0 · 30 days	Unlimited during the trial
BYOK Pro	$6.70 / user / month*	Unlimited

*Billed per user through the Atlassian Marketplace (Paid via Atlassian), in USD. Teams of up to 10 users pay a flat $57/month; volume discounts apply above 100 users, and the Marketplace shows the exact price for your team size. Every plan is Bring Your Own Key — you add your own Anthropic API key, so AI usage is billed to your Anthropic account separately, and the subscription covers only the app itself.

Data & privacy

Spec2Tickets operates no backend. Your page content is sent to Anthropic using your own API key, governed by your agreement with Anthropic — by default Anthropic does not train on API data and retains it only briefly. Page content and breakdowns are stored transiently in Atlassian Forge storage and removed after you push. Full details are in the Privacy Policy.

Troubleshooting

“API key not configured”	Add your Anthropic API key under Settings (Step 3).
Anthropic rate limit / credits	Check your usage tier and billing at console.anthropic.com.
Subtasks created as a checklist	Your Jira project has no Subtask issue type — enable it in project settings, or contact support.
“Subscription required”	Your 30-day trial has ended, or there's no active subscription. Subscribe to Spec2Tickets from the Atlassian Marketplace (or ask your Atlassian site admin) to keep generating.

Support

Questions or issues? Email support@spec2jira.com.