Integration · Jira Cloud
Plan in SprintProof. Build from Jira.
Once a plan is reviewed, its tasks go to a Jira project as issues, with the acceptance criteria and estimate written into each one.
In short
The Jira integration sends a plan’s tasks from SprintProof to a Jira Cloud project as issues. An admin connects Jira once with Atlassian sign-in and picks the project. Then anyone on the plan clicks Send to Jira. Each issue carries the acceptance criteria, the estimate range and blocks links, and sending again updates the issues.
What you get
What it does for the plan.
Acceptance criteria in every issue
The issue description holds the task’s description, its acceptance criteria, one per line, and why the task exists.
The estimate as a range
Each issue states best to worst dev-days and the likely figure, written in the description.
Dependencies as blocks links
When one task depends on another, the two issues are joined with a Jira “Blocks” link.
Labels by type
Each issue is labelled with its task type: frontend, backend, data, test, spike, design or ops.
No duplicates
Sending again updates the summary, description and labels of issues already sent, so the plan and Jira match.
A way back to the plan
Every issue links to its plan in SprintProof, where the review, the estimate and the reasons behind each part live.
How it works
Step by step.
- 01
An admin connects Jira.
In Settings › Connected tools, an admin clicks Connect and signs in with Atlassian. No API tokens are pasted. Connecting only gives permission: nothing is sent yet.
- 02
Choose the destination.
The admin picks the Jira project the issues go to and enters the ID of the issue type to create them as, for example Task. Every plan in the workspace sends to that destination.
- 03
Send the tasks.
On a plan’s Tasks tab, anyone working on the plan clicks Send to › Jira. The plan’s tasks become issues, and a message says how many were created and how many updated.
- 04
Send again after changes.
If the plan changes, send again. Issues that already exist are updated in place instead of duplicated.
What goes into each Jira issue
The summary is the task key and title, for example “[INV-3] Rate limit invite sends”. The description is written in this order:
- The task’s description.
- Acceptance criteria, one line per criterion.
- Why this task exists: the reason from the plan, often a question found in the gap review.
- Estimate: best to worst dev-days, with the likely figure.
- A link to open the plan in SprintProof.
What it doesn’t do
Sending is one way, from SprintProof to Jira. Status changes and comments in Jira don’t come back into the plan. Owners, story points, priority, epics and sprints are not set on the issues; set them in Jira the way your team already does.
The integration works with Jira Cloud. Jira Server and Data Center are not supported.
Disconnecting
An admin can disconnect Jira in Settings › Connected tools. SprintProof deletes its access at once. To remove it fully, the admin also removes SprintProof under Connected apps in their Atlassian account. Issues already sent stay in Jira.
FAQ
Jira: common questions
Does SprintProof sync with Jira both ways?
What happens if I send the same plan twice?
Who can connect Jira and who can send tasks?
Does it work with Jira Server or Data Center?
Does sending tasks cost credits?
Team
Plan the next feature before the sprint starts.
Create your account and name your workspace. Your first feature plan is free. To keep planning, subscribe to Team: the 14-day money-back guarantee applies.
Want to hear when the ChatGPT and Codex plugin ships? Leave your email.