Skip to main content

Import Jira tickets

Quick start​

Connect Jira in NEXT, enable the Teamspace subscription for this import, and let the scheduled sync pull Jira issues into NEXT as Highlights.

Why integrate with Jira?​

Jira is often where support escalations, bugs, and customer requests end up after they leave the inbox. Importing Jira into NEXT helps teams analyze that operational backlog as another source of customer demand instead of treating it only as delivery work.

  • It turns issue-tracking data into analyzable customer signal.
  • It helps teams compare what customers ask for with what has already been escalated internally.
  • It gives product and support leaders a cleaner view of recurring request volume and issue patterns.

What gets imported​

  • Object in NEXT: Highlights
  • Source objects: Jira issues
  • Included fields: Issue title, body text, status, labels, project metadata, and source identifiers for traceability.

Authentication​

Jira credentials configured for the Atlassian integration.

Connection notes​

  • Connect the Atlassian integration with the Jira credentials used for the target workspace.
  • Enable the Teamspace subscription that should receive imported Jira issues.

Configuration notes​

  • Use the subscription configuration to scope the Jira projects or issue types that matter for your Teamspace.
  • NEXT imports new or changed issues incrementally after each successful sync.

Limitations​

  • Only the mapped issue fields are imported into NEXT.
  • Permissions on the configured Jira user control what NEXT can read.

Troubleshooting​

  • If issues stop importing, check whether the Jira credentials still have project access.
  • If expected issues are missing, review the subscription filters and the last successful sync timestamp.

FAQ​

What does NEXT create from each issue?​

Each imported Jira issue becomes a Highlight so teams can analyze support or bug demand alongside other signals.

Does NEXT write back to Jira?​

This import flow is read-only. Outbound Jira actions are separate from the inbound import.