Linear
Connect the Linear workspace your team plans its work in.
Steplane works on its own: change projects, findings, approvals and go-live don't need another tool. If your team plans its work in Linear, connect it, and each tool keeps what it's good at:
- Linear keeps the work: projects, issues, who does what and when.
- Steplane keeps the process knowledge: the live and to-be processes, the impact checks, the approvals and the history. Approvals always stay in Steplane, because auditors read them next to the process versions.
Steplane doesn't copy everything back and forth. It links the two where it helps.
Connecting
Owners and admins choose Connect Linear in Settings → Integrations. Linear asks you to allow Steplane in your workspace; you need to be allowed to add apps there. Afterwards Settings shows which workspace is connected and who connected it.
Steplane acts in Linear as the app Steplane, not as the person who connected it, so it's clear where an issue or a link came from.
One Linear workspace belongs to one Steplane organization at a time.
Disconnecting
Disconnect in Settings ends the connection and removes Steplane's access to the workspace. Removing the Steplane app in Linear's settings does the same, and Steplane notices.
Linking a change project
A change project in Steplane links to one project in Linear: the ERP rollout in Linear, and its process changes in Steplane. On the project page, choose Link to a Linear project…, pick the Linear project and choose Link. Editors can link and unlink.
The Linear project then gets a link back to Steplane in its resources, with a label that says how the process change stands, for example Steplane · In review · 2 open impact warnings, Steplane · Ready to go live or Steplane · Live since 23 Oct 2026. Steplane updates the label within the hour when things change.
The project page in Steplane shows the Linear project and its status. Unlink removes the link on both sides.
Claude can link projects too ("Link the ERP change project to the New ERP project in Linear"), and sees the Linear project when it reads a change project, so it can work across Steplane and Linear if you've connected both.
Findings as issues
Once a change project is linked, the work of fixing its findings can be planned in Linear. Next to an open finding, choose Send to Linear. Steplane creates an issue in the linked Linear project, in the project's team, assigned to the owner of the affected process when Linear knows their email address. The issue describes the finding and has a link back to the project in Steplane.
A finding is sent once. The findings list then shows the Linear issue and its status, such as ENG-12 · In Progress. When the issue is done in Linear:
- a finding someone added is resolved in Steplane, noted as "Done in Linear (ENG-12)"; reopening the issue opens the finding again
- a finding from the impact checks clears itself once its cause is fixed in the process, as always; the issue's status shows how the work stands
Claude can send findings too: "Send the open warnings of the ERP project to Linear."
When things change in Linear
Steplane listens to a few things in Linear, and leaves the rest to Linear:
- The Linear project is completed. The work is done, so the process change is ready for its last steps. The Steplane project's owner gets an email and an item in their inbox under From Linear: mark the project ready for review to ask for the final approval, then go live. Approval and go-live stay in Steplane.
- The Linear project is cancelled. The owner hears about that too, with the suggestion to cancel the Steplane project as well, or link it to another Linear project.
- The target date changes. The project page shows Linear's target date next to the planned go-live. Steplane doesn't move its own date: going live is the owner's decision.
- An issue for a finding changes. Its status shows in the findings list (see above).