Skip to content

Connect Jira to Infograph

What it brings in: issues, projects, users, issue fields, statuses and 4 more.

What you need

  • A Jira Cloud site. Jira Data Center and Jira Server are not supported.
  • An Atlassian account with access to Jira on that site. Infograph reads the projects and issues your account can browse.
  • If your site blocks apps installed by users, ask a site admin to allow Infograph first.

Steps

  1. Open Jira in Infograph

    Open Jira in Infograph and press Continue to Jira. An Atlassian sign-in window opens.

    Continue to Jira
  2. Sign in and choose your site

    Sign in with your Atlassian account. Atlassian asks which site to give Infograph access to. Choose the Jira site you want to analyse: a connection reads one site.

  3. Accept the access request

    Atlassian lists what Infograph asks to read. Press Accept.

  4. Choose what to sync

    Issues brings every issue with its change history, so you can see when each one moved between statuses. Projects, Users, Statuses, Priorities and the other lists explain the codes on each issue. Pick what you want and Infograph starts loading it.

Or connect with an API token

  1. Create an API token with scopes

    Go to id.atlassian.com, open Security, then API tokens, and choose Create API token with scopes. Name it Infograph and pick an expiry date.

  2. Choose Jira and its scopes

    Choose Jira as the app, then tick read:jira-work and read:jira-user. Create the token and copy it. Atlassian shows it only once.

  3. Paste it in Infograph

    Open Jira in Infograph and choose Use an API token instead. Enter your site name (the part before .atlassian.net), the email of the Atlassian account that made the token, and the token, then press Connect. Pick what you want and Infograph starts loading it.

What it syncs

Each becomes a table in Infolake that you can chart, report on or ask about. You choose which to sync.

Issuesissues

Every issue, with its project, type, status, priority, assignee, reporter, story points, sprint and dates, plus each change to its fields over time. The base for cycle time and throughput dashboards.

Ask: “How long do bugs take from creation to resolution, on average, by project?”

Projectsprojects

The projects on your Jira site, with their name and key. Ties every issue to the project it belongs to.

Ask: “Which project has the most open issues right now?”

Usersusers

The people and accounts on your Jira site, with their display name. Turns the account IDs on issues into names.

Ask: “Who has the most issues assigned to them that are still open?”

Custom fieldsissue_fields

Every field on your site, built-in and custom, with its ID and name. Explains what each custom field on an issue means.

Ask: “Which custom fields do we have on our issues?”

Statusesstatuses

The workflow statuses your site uses, such as To Do, In Progress and Done. Groups issues by stage of work.

Ask: “How many issues are in each status across all projects?”

Show all 9 tables
Prioritiespriorities

The priority levels your site uses, such as Highest to Lowest. Lets you sort and filter issues by urgency.

Ask: “How many high priority issues did we close last month?”

Issue typesissue_types

The issue types your site uses, such as Bug, Story, Task and Epic. Splits work into features and fixes.

Ask: “What share of the issues we closed this quarter were bugs?”

Resolutionsresolutions

The ways an issue can be resolved, such as Done, Won't Do or Duplicate. Separates finished work from closed-as-not-needed.

Ask: “How many issues were closed as duplicates last quarter?”

Versionsproject_versions

The versions, or releases, set up in each project, with the project they belong to. Tracks what is planned for each release.

Ask: “How many issues are still open for our next release?”

Troubleshooting

Each entry is the message Infograph shows when a connection fails. Open it for the fix.

Those credentials were not accepted.

Atlassian did not accept the email and token together. Check the email is the one of the account that made the token, and that the token was made with Create API token with scopes: a token made without scopes, or an organisation admin API key, cannot read Jira here. A token that expired or was revoked stops working too: create a new one, open the connection in Infograph, choose Edit configuration and paste it.

Access was not allowed, so nothing was connected. Connect again and choose Allow.

The sign-in was answered with Cancel or Deny, so nothing was connected and Infograph holds no access. Press Connect again and choose Allow. Infograph uses the access only to read and sync your data.

Your account cannot read this data. Ask an admin of the account for access, then connect again.

Jira refused to show this data to your account. Infograph reads with your permissions, so it sees only the projects you can open in Jira. Ask a Jira admin to give you the Browse projects permission on the projects you need, then connect again.

Infograph's access was removed or has expired. Re-authenticate to resume syncing.

Infograph's access to your Jira site was removed or has expired. You or an admin may have removed it in Atlassian, where it shows in your account settings under Connected apps, or an admin uninstalled it from the site. Press Re-authenticate and choose the same site. If syncs keep failing after that, your account may have lost access to Jira or to its projects: check you can still open them.

Common problems

These happen in Jira itself, where Infograph cannot see them.

Your site is not in the list

Atlassian only lists sites where your account has access to Jira. Check you can open Jira on that site with the account you signed in with. If you have several Atlassian accounts, check which one you signed in with.

Atlassian will not let you install the app

Site and organisation admins can block apps installed by users, in Atlassian Administration under Connected apps. Ask an admin to allow Infograph, then connect again.