Integrations
Integrations: send planned tasks to Jira, Linear or CSV
Plan the feature in SprintProof, then hand the tasks to the tool your team builds from.
In short
SprintProof sends a reviewed feature plan’s tasks to Jira Cloud or Linear as issues, or exports them as CSV for any other tool. Each task carries its acceptance criteria, estimate range, type and dependencies. Sending is one way: SprintProof creates the issues and updates the ones it sent, and your tracker stays the place where the work happens.
Where tasks can go
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.
Linear
Once a plan is reviewed, its tasks go to your Linear team as issues, with the acceptance criteria and estimate written into each one.
CSV export
Not on Jira or Linear? Download the plan’s tasks as CSV and open them in a spreadsheet or bring them into the tool you already use.
What gets sent
Each task in the plan becomes one Jira issue, one Linear issue or one CSV row.
| Field | Jira Cloud | Linear | CSV |
|---|---|---|---|
| Summary or title | Task key and title, for example “[INV-3] Rate limit invite sends” | Task key and title | key and title columns |
| Description | The task’s description and why the task exists | The same, in Markdown | why column |
| Acceptance criteria | In the description, one bullet per criterion | In the description, one line per criterion | One cell, one criterion per line |
| Estimate range | Best to worst dev-days and the likely figure, in the description | The same, in the description | best, likely and worst columns |
| Labels | One label for the task type, such as frontend or backend | One label for the task type, created on the team if missing | type column |
| Dependencies | A “Blocks” link between the two issues | A “blocks” relation | depends on column with task keys |
| Link back to the plan | Yes, to the plan in SprintProof | Yes, to the plan in SprintProof | No |
| Owner, priority, sprint | Not set: set them in Jira | Not set: set them in Linear | owner and status columns |
Connecting
A workspace admin connects once, in Settings › Connected tools: Connect, then sign in with Atlassian or with Linear. Nobody pastes an API token. The admin then picks where issues go: a Jira Cloud project and issue type, or a Linear team and, if you want, a project.
After that, anyone working on a plan clicks Send to › Jira or Send to › Linear on its Tasks tab. A message says how many issues were created and how many updated. Each sent task then shows its issue key, linking to the issue, and the last status SprintProof read from the tracker.
One way, not two-way
The send goes from SprintProof to your tracker. It does not keep the two in step.
- What SprintProof changes: it creates an issue for each new task and, when you send again, updates the issues it sent. In Jira it rewrites the summary, description and labels; in Linear the title, description, label and project. Edits made to those fields in the tracker are replaced.
- What it never touches: issues it did not create, comments, assignees, priority, sprints or cycles, and the issue’s status. Nothing is deleted.
- What does not come back: status changes, comments and edits in the tracker do not change the plan. The last status read back is shown next to the task, for reference.
Using another tracker? CSV export
Not on Jira Cloud or Linear? Download the plan’s tasks as a CSV file from the Tasks tab, with nothing to connect. The file is UTF-8 with a header row naming the columns, and the estimate range stays as three columns. See CSV export for every column.
Do sends cost credits?
No. Connecting a tracker, sending tasks, sending again and downloading the CSV never use credits. Only AI actions do, such as drafting the tasks from the plan’s parts. The tasks themselves start in the feature breakdown, and each one gets acceptance criteria like the ones in the acceptance criteria template and the user story template.
FAQ
Common questions
Does SprintProof sync with Jira or Linear both ways?
Does it work with Jira Server or Data Center?
What happens if I send the same plan twice?
Who can connect Jira or Linear?
Do integrations use AI credits?
Which other tools can I import the CSV into?
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.