Jira integration
Last reviewed:
Issue tracker
Your tickets already describe the work — import them so sessions, reports, and agents can reference real issues instead of retyping them.
Issues assigned to you in Jira Cloud become Kiantu tasks — status stays in sync on every poll.
Issues sync into Kiantu tasks with deep links back to JiraProjects map automatically; status categories translate cleanlyOAuth once, then scheduled sync keeps it fresh
What it does
- Pull-based: Kiantu polls Jira for issues assigned to you that changed since the last sync (15-minute cycle, plus manual “Sync now”).
- Issues materialize as Kiantu tasks (with their Jira project as a Kiantu project); re-syncs update, never duplicate.
- Status maps by Jira status *category* (To Do / In Progress / Done), so custom workflows like “In Review” or “QA” map correctly.
Setup
- 1 In Kiantu, open Settings → Connectors, find Jira and click Connect.
- 2 Approve the Atlassian consent screen. Requested scopes: read:jira-work, read:jira-user, offline_access — read-only.
- 3 Kiantu resolves your Jira Cloud site automatically and runs the first import (last 30 days of assigned issues).
- 4 Imported tasks carry their Jira issue key (e.g. KAN-12) and deep-link back to Jira.
Data & privacy
- Read-only scopes — Kiantu never writes to your Jira instance.
- Only issues assigned to the connected user are imported.
- OAuth tokens are envelope-encrypted at rest; Atlassian’s rotating refresh tokens are handled automatically.
Self-hosting
Server operators enable this integration with the following environment variables (workspace users on app.kiantu.com never need these):
JIRA_CLIENT_IDJIRA_CLIENT_SECRETJIRA_REDIRECT_URI