Skip to main content

Share to Jira

Rick avatar
Written by Rick
Updated this week

Quick start

Connect Jira once in Settings → Integrations → Jira → Connect. Set up one or more Jira connections (Base URL, Project ID, Issue Type). Then, from any Thread, Highlight, or Cluster, click Share → Share to Jira → choose your Jira connection → Share. This creates a Jira issue with your insight text and a link back to the video evidence in NEXT AI, so engineering has everything needed to act.

Why integrate with Jira

NEXT AI turns customer interactions into actionable insights with evidence. Creating a Jira issue directly from a Thread, Highlight, or Cluster sends that signal into the place where teams track and complete work (issues are Jira’s core work items) and prioritize it on the backlog. The issue includes a traceable link back to the original video/context in NEXT AI, so engineers and PMs can validate the problem before acting—reducing rework and speeding decisions.

  • What NEXT AI creates: A Jira issue in the Project and Issue Type you saved in your Jira connection.

  • What’s included: Summary/Description from your insight, plus a link to the video evidence in NEXT AI.

  • Where it lands: The configured project under the selected issue type (e.g., Bug, Story). If your Jira project enforces required fields, your admin may need to expose them on Create.

  • Source: Atlassian REST docs for create metadata (project/issue-type fields) and KB guidance for required fields that block creation.

Connect Jira (one-time)

  1. In NEXT AI, click your profile photo (top right) → Settings

  2. Open Integrations → Jira → Connect

  3. Click New connection and give it a clear name (e.g., “Jira—Bug”, “Jira—Story”)

  4. Enter your Jira Base URL, Project ID, and Issue Type, then Save

Finding IDs in Jira: Atlassian documents how to get a Project ID via REST and how to locate an Issue Type ID in Jira Cloud. Share these with your Jira admin if you need help. In case you're struggling to set it up correctly, reach out to our support team via the pink bubble in the bottom right or send us an email at support@nextapp.co. We'll help you further!

⚠️ Important note: You can create multiple connections for different issue types (Bug, Task, Story, Epic) and pick the right one when sharing.

Create a Jira Issue from NEXT AI

You can share Thread, Highlights, and Clusters to Jira.

  1. Open the item (Thread / Highlight / Cluster)

  2. Click Share → Share to Jira

  3. Choose the Jira connection you created (e.g., “Jira—Bug”)

  4. Optionally edit the text, then Share — NEXT AI creates the Jira issue with a source link back to the evidence.

Tips

  • Name connections by issue type (“Jira—Bug”, “Jira—Story”) so it’s fast to choose the right target at share time.

  • Keep your Summary tight; Jira’s Summary field is short-text (commonly capped at 255 chars). Put detail in the description and let the NEXT AI link carry the context.

Troubleshooting

  • Jira isn’t in the Share menu. Connect it first in Settings → Integrations → Jira.

  • Required field”/issue creation failed. Some Jira projects enforce required fields on the Create screen or via workflow validators. Ask a Jira admin to surface those fields on Create or relax the validator.

  • 403/permission error. You need Create issue permission in the target project (managed via project permission schemes/roles). Contact your Jira admin.

  • Wrong project/issue type. Re-check the Project ID / Issue Type ID you configured (see Atlassian methods above).

FAQ

Q: What exactly does NEXT AI send to Jira?

An issue using your insight’s title/summary + description, plus a link back to the original evidence in NEXT AI so devs can verify the signal before acting.

Q: Can I choose project or issue type each time I share?

Choose among your saved Jira connections (each encodes Base URL, Project ID, Issue Type). Create multiple connections (e.g., Bug, Story, Task) and name them clearly to pick the right one quickly.

Q: Will NEXT AI upload the actual video into Jira?

NEXT AI links back to the video and supporting context. This keeps the evidence authoritative in NEXT AI while letting Jira remain the system of action.

Q: Why create the issue from NEXT AI instead of typing it in Jira?

You move insight + proof in one step, preserving a traceable link to the source. It reduces back-and-forth and helps teams prioritize with confidence.

Q: Who can open the evidence link from the Jira issue?

Only users who already have permission to view that item in NEXT AI. Linking from Jira doesn’t bypass NEXT AI access controls.

Q: Our project rejects the issue, saying a field is required. What should we do?

Ask your Jira admin which fields are enforced for Create in that project (via field configuration or workflow validators) and expose them on Create—or relax the validator—so the issue can be created from NEXT AI.

Q: What’s the best way to keep Jira issues actionable from NEXT AI?

Use a concise Summary (under 255 chars) and a clear first sentence in the Description. Let the NEXT AI link provide rich context (video, Highlights, related Threads).

Q: Can we maintain different targets (e.g., Bugs to ENG project, Stories to PM project)?

Yes—create separate Jira connections per project/issue type and select the right one at share time.

Did this answer your question?