Issue trackers
Spectr drafts the stories. Linear is where the approved ones go. Connect a Linear team and each story you approve becomes a Linear issue with its description, acceptance criteria, priority, labels, estimate and assignee in place. Whenever you refresh story status, Spectr reads each issue's state back, so what is finished in Linear is what Spectr and your budget forecast believe is finished. A cancelled issue counts as cancelled, not quietly as done.
How Linear fits in
A call is imported from a note-taker (Fathom, Granola, Read.ai, or Fireflies.ai). Spectr picks out a requirement, a bug, an action item and an out-of-scope ask, and drafts a story and a bug with acceptance criteria. A person approves both, they are published to Linear, and the requirements, scope log and project memory update from the same call.
OAuth. You authorise Spectr on Linear's consent screen, then pick the team in Spectr. Tokens rotate on every refresh, and Spectr stores each new pair itself.
A Linear workspace, and a decision about which single team this project publishes to. One Spectr project maps to one Linear team.
In Spectr, open the project and go to Integrations.
Choose Linear and click Connect, then authorise on Linear.
Select the Linear team new issues should be created in.
Generate stories from a meeting and open the review page.
Approve the ones you want - individually or in bulk - and publish. Each story in Spectr links to its Linear issue.
Anything else? Email hello@crowdlinker.com and a person will answer.
Spectr records it as cancelled - a terminal state of its own - rather than counting it as done, so dropped work never inflates delivery progress or the budget projection.
Yes. A story can be published to more than one tracker, and Spectr only marks it done when every tracker it went to reports it done.
Not routinely. Linear rotates its refresh tokens and Spectr updates both tokens atomically on every refresh, well ahead of the 24-hour access-token expiry.
Members of the Linear team the project publishes to. Spectr syncs them into the project team, so an assignee picked in review is a real Linear user.
Use case
Draft stories with real acceptance criteria, then approve, edit or reject each one
Publish stories as Jira issues, with sub-task nesting, and read their status back
Publish stories into a Shortcut team and read their workflow state back
Import a Fathom call and get structured specs and stories from its notes, action items, and transcript
Native Granola import - no Zapier, no scripts - straight through to Jira, Linear or Shortcut
Read.ai
Fireflies.ai