Linear, Jira, GitHub and Asana

A play is only useful once someone owns it. Hand off on a play’s page creates an issue in Linear, Jira Cloud, GitHub or Asana with the evidence, the change, the steps, and how the acceptance check will tell that it shipped, with a link back to the play. The issue is kept on the play, so a second press returns the same issue instead of a new one. Hand-offs come with Growth and the plans above it.

For a coding agent rather than a tracker, the same button gives a brief for Claude Code or Codex; see Working a play.

Connect Linear

1. In Linear, create a personal API key (Settings, Security & access, Personal API keys).
2. In Vercatus, Settings, Integrations, Linear: paste the key, enter the team key (the prefix of the team’s issues, such as ENG) and optionally a project id.
3. Save, then Check the connection. The check signs in and looks the team up without creating anything.

Connect Jira Cloud

1. Create an API token at id.atlassian.com (Security, API tokens).
2. In Vercatus, Settings, Integrations, Jira Cloud: the site URL, the email of the account the token belongs to, the token, the project key, and the issue type (Task unless you say otherwise).
3. Save, then Check the connection. The check reads the project and confirms the issue type exists.

Connect GitHub Issues

1. In GitHub, create a fine-grained token (Settings, Developer settings, Fine-grained tokens) for the one repository, with Issues read and write.
2. In Vercatus, Settings, Integrations, GitHub Issues: the token, the repository (owner/name) and, if you like, labels to add to every issue.

Connect Asana

1. In Asana, create a personal access token (My settings, Apps, Developer apps, Personal access tokens). Tasks are created as its owner.
2. In Vercatus, Settings, Integrations, Asana: the token and the project, the number in the project’s address.

When a tracker refuses

When a tracker refuses an issue (an expired token, a missing project, a field it requires), nothing is kept on the play and the hand-off says why, in the tracker’s own words.

Site audit findings

Findings from the site audit can also be sent on their own through the API: POST /api/findings/:id/ticket with { "provider": "linear" }, and POST /api/findings/tickets with { ids, provider } for many at once. A finding that already has an issue is never exported twice, and when a later run verifies the fix, the result is posted as a comment on the issue.

What is stored

Tokens are stored with the workspace and used for nothing but the calls above. They are never returned to the browser; the settings page shows that a token is set. Replacing it means pasting a new one; Remove deletes the integration and its token.