Linear completed issues
One GraphQL query per page over the issues completed inside the window, and five fields on each: its id, its identifier, its url, when it completed and which team and state it is in. Never a description, never a comment.
Access
- Kind
- A read-only key you paste
- What to give
- Personal API key
- Why that one
- A Linear API key that can read issues. This source writes no spend: it reports what the spend produced.
What it attributes on its own
- From the source
- issues completed per day, at the moment each completed · the team and the state each carried · a link to the issue itself
- Needs a rule or a trace
- which issues an assistant helped with — Linear records no such thing, so cost per completed issue is a floor on the cost per assisted one · the workflow, which you tell us · how large an issue was: a project and a typo both count as one
The addresses it calls
- https://api.linear.app/graphql
Only these. A call anywhere else is refused before it leaves, and every call is logged.
Connecting it
- Create a personal API key. Settings → Security & access → Personal API keys. It carries your own read access and nothing more. Open ↗
- Name the workflow these count for. The workflow your assistants serve. Its spend divided by these completions is your cost per delivered issue.
- Paste both and click Test and connect. Valistry reads the last seven days of completions, reports how many, then fills thirty.
Linear has one completion concept for every workspace, so unlike Jira there is no query for you to write. Where your assistants write the issue identifier into a trace, we can join issue to spend exactly instead of by workflow.