Skip to content

Other apps

Connect Jira to DataxLand

The Jira connector reads issues, change history, comments, projects, sprints, versions and users from Jira Cloud. For IT teams that run their help desk or incident tracking in Jira, Si maps issues by type and priority to the IT tickets, incidents and changes of the standard model, so you get ticket counts, P1 incidents, mean time to resolve and change failure rate; add your orders and you also see IT tickets per 1,000 orders.

Free plan with no time limit · No card required · Sample workspace ready in minutes

What you can do with Jira

  • Track MTTR and P1 incident counts month by month.
  • Measure change failure rate when change issues are tagged with their deployment outcome.
  • Set an alert when the day's IT ticket count crosses a threshold.

What data you get

Each stream lands as its own table in the workspace warehouse, as is; personal-data columns are hashed on load.

Stream (table)Contents
issuesIssues with type, status, priority, assignee, created and resolved times; loaded incrementally.
issue_changelogsStatus change history, used to compute response and resolution times.
issue_commentsComments; select only when you need them.
projectsProjects, used as the service dimension.
issue_prioritiesThe list of priority levels.
sprintsSprints of Scrum boards.
usersJira users; emails are hashed on load.

Connection details

Sign-in methodConnection details (API key, account), encrypted at rest
Sync modesFull (reloaded each run) · Incremental (new or changed rows only)
Fields to fill inAuthentication, Domain
DeveloperAirbyte (certified), run inside DataxLand
LicenseELv2

Passwords and keys are encrypted at rest. Personal-data columns are hashed on load.

Metrics computed from this source

Real definitions from the analytics packs; dashboards and Si share them.

MetricDefinitionUnit
IT support ticketsNumber of IT support tickets (incidents and requests) opened in the period, by open date.Count
IncidentsNumber of incident-type tickets opened in the period, by open date.Count
P1 incidentsNumber of highest-priority incidents (P1, critical) opened in the period.Count
Resolved incidentsNumber of incidents resolved in the period, by resolution date.Count
Mean time to resolve (MTTR, hours)Average hours from open to resolution for incidents resolved in the period.= it_incident_hours_total / Resolved incidentsNumber
Average first response time (hours)Average hours from ticket creation to first response, across all tickets opened in the period.= it_response_hours_total / IT support ticketsNumber
Changes deployedNumber of IT changes deployed in the period, by deployment date.Count
Change failure rateFailed changes (failed or rolled back) divided by changes deployed in the period.= Failed changes / Changes deployedRatio (%)

Connect Jira in 4 steps

  1. 1

    Create an API token

    On your Atlassian account security page, create an API token for an account that can view the projects you need.

  2. 2

    Add the Jira source

    In the workspace choose Add source, find Jira, enter the Domain (yourcompany.atlassian.net), choose API Token, enter the email and token; limit Projects if you only need a few.

  3. 3

    Choose streams

    Click Test connection, then select issues, issue_changelogs, projects and issue_priorities.

  4. 4

    Review and build

    Si proposes which issue types count as tickets, incidents or changes; you confirm, then build the IT dashboard.

Limits and caveats

  • Jira has no built-in, shared notion of an incident or SLA; the classification by issue type and priority is something you approve, and it is then used for every metric.
  • Service availability needs outage duration data (PagerDuty or a file); it cannot come from Jira.
  • Atlassian rate-limits API calls; large sites take longer on the first load.
  • Requires the Starter plan or above. An Airbyte connector (ELv2) run inside DataxLand.

Frequently asked questions

Does it work with self-hosted Jira Server or Data Center?

Only if the server has a public address; DataxLand blocks private network addresses when connecting.

Do issue descriptions reach Si?

Si sees a masked data sample when proposing the mapping; Si's answers are based on metrics and never return issue content.

Does it create or edit issues?

No. The connector is read-only.

Dashboard templates that use this source

Ask Si about your Jira data →All data sources →

Connect Jira and get verified dashboards

Free plan with no time limit · No card required · Sample workspace ready in minutes