Linear
Linear sits behind the same interface as Jira: ticket badges on board rows, status you can change from there, and cycles that scaffold worktrees. It is built and it ships in the app — the one piece that is not live yet is the connection.
Heads up
You will find Linear under Settings, then Connections, and pressing Connect will not work today. The flow goes through Strado's hosted OAuth broker, and that broker is not switched on yet. Nothing is wrong with your install — the missing half is on our side, and there is no local workaround to reach for.
What it will do
Everything the Jira page describes, with two differences that come from Linear itself rather than from Strado.
| Jira | Linear | |
|---|---|---|
| Ticket keys | FD-12 | ENG-45 |
| Iterations | sprints, per project | cycles, across every team you can see |
| Estimates | time, as 2d 4h | points, as a number |
| Logged and remaining time | shown on the hover card | Linear has no equivalent, so neither is shown |
Both providers can be connected at once. A worktree records which system its ticket belongs to, so a Jira board and a Linear board coexist in one workspace rather than one displacing the other.
Status, from the board
A Linear issue's workflow state shows in the row's Status column, mapped through the same three categories Strado uses everywhere — to do, in progress, done — which is also what decides whether a row counts as settled and sinks to the bottom of the board.
Changing it there performs a real update in Linear. The dropdown offers that issue's team's own workflow states in the order the team arranged them, so it reflects your team's process rather than a generic three-step one.
Cycles
Linear's cycles take the place of sprints. Strado reads active and upcoming cycles across every team the account can see, rather than asking you to choose a project first, and the import flow can scaffold a worktree per issue in the cycle exactly as it does for a Jira sprint. Issues already finished are left out.
What connecting will involve
Not a procedure — there is nothing to follow yet — but worth knowing what it will and will not ask of you.
It is an OAuth flow, so you will authorise Strado in your browser rather than
paste a token. The client secret stays with the hosted broker; it is never in
the app or on your machine. What comes back is an access token, and that is
written to ~/.strado/linear.json, alongside your workspace name, with
permissions 0600 when Strado creates it — see
files and locations for the caveat on a
file that already exists.
From then on it behaves like every other connection here: the token stays on the machine, every Linear call is made by the local server, and the interface can only ask whether a connection exists — it never reads the token back.