Connect Jira

Jira says what the work was for: issues, epics, sprints and story points. Connect it with a Jira user's API token, then pick the projects your engineering teams work in.

Before you start

You need a Jira Cloud site (yourcompany.atlassian.net) and a Jira user that can browse the projects you want tracked. A dedicated service account is best: the connection keeps working when people leave, and you can see exactly what it has access to. We only read; nothing is ever written to Jira.

Create an API token

1. Sign in to Atlassian as that user and open id.atlassian.com → Security → API tokens.
2. Press Create API token, name it “Truly Shipped”, and copy the token.

Connect

1. On Connections, fill in the Jira card: your site, the user's email and the API token, then press Check and find projects.
2. We check the details with Jira and list every project that user can see. Tick the ones your engineering teams work in, and press Connect Jira.

History starts syncing right away. To change the projects later, open Change details on the card; leave the token blank to keep the current one.

Company-managed and team-managed projects

Jira has two kinds of project. Company-managed projects work fully. Team-managed projects store sprints and epics differently, so some of them may not come through; the project list marks these. Issues, statuses and story points still arrive. If your sprint or epic numbers look thin for a team-managed project, that's why.

Live updates (optional)

Without a webhook, Jira changes arrive with the nightly sync. With one, they arrive within 15 minutes. Once Jira is connected, open Live updates on the Jira card for your workspace's own URL and secret. Then a Jira admin:

1. Opens Jira Settings → System → WebHooks → Create a WebHook.
2. Pastes the URL and secret from the card.
3. Sets the JQL to the line the card shows, for example project in (PAY, WEB).
4. Ticks the issue events created, updated and deleted, leaves “Exclude body” unticked, and saves.

Keep the secret private: it's what proves the updates come from your Jira. If you add projects later, update the webhook's JQL to match.

Checking it works

The Jira card shows Working and when it last synced. Test connection checks the token. If the token expires or the user loses access, the card says so and what to do next; the usual fix is a new token under Change details.