Jira Integration
Ingest tickets and incidents for Delivery and Quality signals.
Why connect Jira
Jira is a Product Tracking source. After you connect, the platform reads your Cloud site’s issues on a schedule and uses them for Delivery (tickets created and completed) and Quality (incident-type issues declared and resolved), including planning-time signals when available.
The integration is read-only. We never create, update, or delete issues in Jira.
What you need
- A Jira Cloud site (for example
https://your-domain.atlassian.net). - An Atlassian account email with access to the projects you want reflected.
- An API token created for that email at Atlassian API tokens.
Select Jira in your tech stack under Product Tracking if you use it today.
Setup
- In Atlassian, create an API token for the account email you will use.
- In the platform, go to Settings → Integrations (or onboarding Integrations) and choose Connect on Jira.
- Enter the Site URL, Email, and API token.
- Click Test connection. A successful test shows the Atlassian display name for that account.
- Click Connect (or Save changes) to store encrypted credentials.
Issues sync on the platform’s productivity-ingest batch schedule after the first successful save.
Data we read
| Jira data | Platform use |
|---|---|
| Incident-type issues (open / resolved) | Quality metrics, MTTR |
| Story/Task-style issues created | Delivery (ticket created) |
| Story/Task-style issues completed | Delivery (ticket completed) |
| Time in planning statuses (when enabled) | Delivery (planning time) |
We also keep lightweight assignee and reporter identifiers (accountId, falling back to
display name) on those events so activity can be attributed. We do not sync a full Jira people
directory or org chart.
Data we do not read or change
The integration is read-only. We never write to your Jira site.
| Not accessed | Notes |
|---|---|
| Confluence | Separate connector (not this integration) |
| Jira admin / user management APIs | Not used |
| Issue create/update/delete | Never performed |
| Service Management deep admin | Out of scope for v1 |
Sync schedule
After connect, the platform syncs on the productivity-ingest batch schedule alongside other productivity sources (GitHub, Bitbucket, PagerDuty, and related incident tools). There is no dedicated Sync now button for Jira yet — the next scheduled batch run picks up new credentials automatically.
Disconnect
From the Jira connected card, choose Disconnect. That removes the stored source for the workspace and stops new polling. Historical metrics already computed for the workspace remain until cleared by other means.