# Jira BI and Analytics — Connect to Supaboard

> Ask questions of your Jira data in plain English and see the SQL behind every answer.

HTML version: https://supaboard.ai/integrations/jira

Jira holds the issues, the sprints, the cycle times and every workflow state your team has invented.

## What teams ask of Jira

- "What is cycle time by issue type, and which state does work actually sit in?"
- "How much of last quarter went to unplanned work?"
- "Which epics have been in progress longest without a status change?"
- "What is the ratio of bugs to features by team, over time?"

## What it gets joined with

- Zendesk Support — the engineering work, against the tickets that prompted it.
- Sentry — the issue, against the errors it was meant to fix.

## How the connection works

Jira is one of the 124 sources you can connect yourself, out of a catalogue of 700+. It syncs through Fivetran on a schedule — the first sync lands within a day and refreshes hourly to daily after that — so answers are over the last completed sync, not a live feed. Databases connect directly and answer live.

- Read-only: the query layer rejects DDL and DML before a statement reaches your source.
- Credentials encrypted at rest, scoped per workspace, never logged.
- On-premise deployment with no data egress on Enterprise: https://supaboard.ai/enterprise
- From $83 per user/month billed annually: https://supaboard.ai/pricing

## More

- [All connectors](https://supaboard.ai/integrations)
- [Compared with the major BI platforms](https://supaboard.ai/compare)
- [What an AI data analyst does](https://supaboard.ai/)

---

- Site index for agents: https://supaboard.ai/llms.txt
- Sitemap: https://supaboard.ai/sitemap.xml
- Blog feed: https://supaboard.ai/blog/rss.xml
- Product documentation: https://docs.supaboard.ai

Any page on https://supaboard.ai is available as markdown: append `.md` to its path, or send `Accept: text/markdown`.