Integration · Linear
Plan in SprintProof. Build from 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.
In short
The Linear integration sends a plan’s tasks from SprintProof to a Linear team as issues, optionally inside a project. An admin connects Linear once and picks the team. Then anyone on the plan clicks Send to Linear. Each issue carries the acceptance criteria, the estimate range and blocks relations, 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 and why the task exists, in Markdown.
The estimate as a range
Each issue states best to worst dev-days and the likely figure, written in the description.
Dependencies as blocks relations
When one task depends on another, the issues get a Linear “blocks” relation.
A label by type
Each issue gets one label for its task type, such as frontend, backend or data. SprintProof creates the label on the team if it is missing.
No duplicates
Sending again updates the title, description, label and project of issues already sent, even archived ones.
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 Linear.
In Settings › Connected tools, an admin clicks Connect and signs in with Linear. No API keys are pasted. Connecting only gives permission: nothing is sent yet.
- 02
Choose the team and project.
The admin picks the Linear team the issues go to and, if you want, a project inside it. Every plan in the workspace sends there.
- 03
Send the tasks.
On a plan’s Tasks tab, anyone working on the plan clicks Send to › Linear. 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 instead of duplicated.
What goes into each Linear issue
The title 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 Linear. Status changes and comments in Linear don’t come back into the plan. Assignees, Linear estimates, cycles and priority are not set on the issues; set them in Linear the way your team already does.
Disconnecting
An admin can disconnect Linear in Settings › Connected tools. SprintProof revokes its access in Linear and deletes it on its side. Issues already sent stay in Linear.
FAQ
Linear: common questions
Does SprintProof sync with Linear both ways?
What happens if I send the same plan twice?
Can tasks go into a Linear project or cycle?
Who can connect Linear and who can send tasks?
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.