CONNECTOR · JIRA
Your plan, pushed to Jira in one click.
A connector is the bridge to your issue tracker. This one turns a Ready plan into Jira issues: nested, ordered, pointed, and set for your dev team to pick up. It reads the other way too: bring an epic that is already in Jira into a plan, refine it with the agent, and push it back to the same issues.
What lands where
Push a Plan and every part of it maps to something native in Jira. No copy and paste, no reformatting.
| In Plansmith | In Jira |
|---|---|
| Project | Project |
| Spec | Issue |
| Child Spec | Sub-task |
| "Needs first" link | "Is blocked by" link between issues |
| Effort (Low · Med · High) | Story points |
| Readiness (Rough · Shaping · Ready) | Status. Every pushed issue lands in your team's default starting status today, ready to pick up. |
| Acceptance criteria checklist | Checklist in the issue description |
Three steps to a full board
- 1
Connect
Click Connect Jira and sign in with your Atlassian account. The connection belongs to you, not your whole site, and takes about a minute. If your site requires an admin to approve new apps, send them this page.
- 2
Review
Pick the Jira project your Plan should land in. Before anything reaches Jira, you see a preview: how many issues, and where each Spec lands.
- 3
Push
One click. A confirmation appears: "Pushed 14 issues to Jira." Every Spec keeps a link to its issue, so you can jump straight from the plan to the board.
Questions, answered
- What happens if I push the same plan again?
- Plansmith remembers which issue belongs to which Spec. A re-push updates the issues for Specs that changed in Plansmith and creates issues for new ones. Issues for unchanged Specs are left alone, and issues your team created themselves are never touched. If somebody edited one of your issues since the last push, Plansmith stops before writing and the agent walks you through it, so their work is never overwritten without you deciding.
- My Spec tree is four levels deep. What happens?
- It lands four levels deep. Child Specs become sub-tasks at every level, wired to their direct parent.
- Who needs to connect Jira?
- Whoever clicks Push. Connections are personal, so a teammate who pushes needs their own. Everyone else can still plan, comment on Specs, and export, and they see the issues appear in Jira.
- Do I need Jira before I start planning?
- No. Plan first, refine until it's Ready, and export it as a document (Markdown) or a spreadsheet (CSV) in the meantime. Connect Jira whenever you want the one-click push.
Handed off, not handed back.
Explore other connectors: Linear · Asana · Radial · All connectors