Quick start

From the Teamspace where you want data to land, open Settings → Integrations → Jira → Connect, enter your Atlassian account email (Jira Cloud) and API token, then create a subscription to auto-import new Jira issues as Highlights in this Teamspace. Jira Cloud REST uses email + API token for Basic auth.

Why integrate Jira?

Jira issues capture real customer demand (bugs, requests, escalations). Bringing them into NEXT AI alongside calls, tickets, surveys, and reviews creates a richer customer-intelligence graph so teams can prioritize with verifiable evidence and push outcomes back into delivery tools.

What gets imported

Object in NEXT AI: Highlight (short-form signal) in the connected Teamspace.
Typical fields (when available from Jira):
issue key (e.g., PROJ-123), summary, description/latest comment, status, priority, issue type, assignee, reporter, labels, timestamps, and a source link back to the issue. (All are available via the Jira Cloud Issues REST resources.)

Connect Jira

Create an Atlassian API token (or a service-account token) and copy it.
In NEXT AI, open Teamspace → Settings → Integrations → Jira → Connect.
Enter your Atlassian account email (Cloud) and API token → Save.

Jira Cloud REST authenticates with email + API token (not your password). Works with 2FA/SAML.

Permissions in Jira control what NEXT AI can read; ensure the token user can Browse projects you want to import.

Auto-import tickets

Create a subscription that watches for new Jira issues and creates a Highlight for each one:

Scope: start with key project(s) and expand; your Jira permissions apply.
Freshness: choose a start date/time, then imports continue automatically.
Event-driven (optional): Jira webhooks can push create/update events to reduce polling; admins manage these in Settings → System → WebHooks.

Tips

Route by labels & status: map Jira labels/status to NEXT AI Labels for instant triage.
Ground Threads: when teammates ask questions in Threads, answers can point back to the imported issue’s source link.
Plan for limits: Jira Cloud returns HTTP 429 when you exceed rate limits—batch backfills and retry with backoff.

Troubleshooting

401/403 on connect → Re-enter the email + API token pair; tokens are required for Cloud REST.
Nothing is importing → Confirm the subscription is active and the token user has Browse permission on the project(s).
Slow or throttled (429) → You’re hitting Jira Cloud rate limits; reduce concurrency and add exponential backoff.
We prefer push → Use Jira webhooks for create/update events; admins configure these in System → WebHooks.
Server/Data Center → Auth differs (password/OAuth options). If you use Data Center, follow its Basic/OAuth guidance.

FAQ

Q: What exactly is created in NEXT AI from Jira?

A Highlight per new issue, including summary/description, status/priority/type, assignee/reporter, labels, timestamps, and a source link to the issue.

Q: Do we need both the email and the token?

For Jira Cloud, yes—REST auth is email + API token (your password won’t work).

Q: Can we limit imports to specific projects or issue types?

Yes—scope your subscription to selected projects and filter by type/labels as needed (your Jira permissions still apply).

Q: Do you import sub-tasks and custom fields?

Core fields are imported by default. If your workflow depends on custom fields, add them to your Jira view schemes; they’re available via the Issues REST resources and can be mapped in NEXT AI.