Connect Jira
Create an Atlassian API token in three steps, see what Sprint Radar reads, and how to revoke access.
Sprint Radar reads your Jira Cloud data with an Atlassian API token. You create the token yourself, in your own Atlassian account, and you can revoke it at any time.
Create the token in three steps
- Open
id.atlassian.com/manage-profile/security/api-tokensand choose “Create API token”. - Give it a name, for example “Sprint Radar”, choose an expiry date, and copy the token. Atlassian shows it once.
- In Sprint Radar, choose “Connect Jira” and enter your site address (for example
your-team.atlassian.net), the email of your Atlassian account and the token.
If the site address, the email or the token is wrong, the dialog says which field and why. It does not save a connection that failed.
What Sprint Radar reads
- Issues of the projects you choose, all of them: Sprint Radar reads every page of the search results, so a large project is read in full. It uses the type, status, resolution, dates, story points, assignee, creator, labels, sprint and the issue summary. It does not use descriptions or comments.
- Story points come from the “Story Points” field. If your site has no field of that name, the first field whose name contains “story point” (for example “Story point estimate”) is used.
- The history of status changes of those issues. Cycle time and rework are measured from it.
- Sprints and their dates, for the sprint calendar.
- The list of statuses of your Jira site, to know which statuses mean “in progress” and “done”.
Reports show issue summaries. Anyone who can open a report, or a share link of it, can read them. Share links say so before you create one.
Jira Cloud only
The site address must be https://your-team.atlassian.net. Sprint Radar sends your token to that host only, does not follow redirects, and refuses any other address. Jira Server and Data Center are not supported. Every call to Jira has a time limit of 30 seconds, and a busy or failing Jira (HTTP 429 or 5xx) is retried up to four times with growing pauses before the forecast fails with a message.
Work closed without delivery
An issue closed with the resolution Won't Do, Won't Fix, Duplicate, Cannot Reproduce or Declined is treated as not delivered. It does not count as done work and it does not count as scope growth. The cycle time of such an issue is left out too.
Read-only use
Sprint Radar only asks Jira for data. It does not create, change or delete anything in Jira. The token has the rights of your Atlassian account, so Sprint Radar can read what that account can read. If you want to limit it, create the token with an account that can see only the projects you want to forecast.
Where the token is kept
The token is stored encrypted and is never shown again after you save it.
Revoke access
- At Atlassian: open the same API tokens page and revoke the token. Access stops at once.
- In Sprint Radar: delete the project. Deleting the whole workspace removes everything, see Delete your data.