Skip to main content

Share to Jira

Use Share to Jira when you want to turn evidence from NEXT into a Jira issue in a specific project and issue type.

Jira sharing is configured through named connections in Settings → Integrations → Jira. Each connection stores the Jira base URL, project ID, and issue type that NEXT should use when it creates the issue.

Before You Start​

  • Open the teamspace where you want to configure the Jira connection.
  • Make sure you know your Jira base URL.
  • Have the Jira Project ID and Issue Type ready for the destination you want to use.
  • Make sure you have permission to create issues in that Jira project.

Steps to Connect (One-Time)​

  1. In NEXT, open Settings → Integrations → Jira.
  2. Click Connect.
  3. Create a new connection and give it a clear name, such as Jira - Bug or Jira - Story.
  4. Enter the Jira Base URL, Project ID, and Issue Type.
  5. Save the connection.
  6. Repeat this setup for any additional Jira projects or issue types you want to target.

Steps to Share​

  1. Open the chat, highlight, or cluster you want to share.
  2. Click Share and choose Jira.
  3. Select the Jira connection you want to use.
  4. Review the share text and confirm the share.

NEXT creates a Jira issue in the configured project and issue type and includes a link back to the source in NEXT.

When Should I Use Jira?​

  • Use Jira when your team needs feedback routed directly into an existing Jira workflow.
  • Use separate Jira connections when different teams, projects, or issue types should receive different kinds of work.
  • Use Jira when traceability matters and you want the issue linked back to the original evidence in NEXT.

Tips​

  • Name Jira connections after the destination they create, not just the tool itself.
  • Keep the summary short and put extra context in the description.
  • If issue creation fails because Jira requires additional fields, ask your Jira admin to review the create-screen requirements for that project and issue type.

Troubleshooting​

  • Jira is not available in the share menu. Connect Jira first in Settings → Integrations → Jira for the current teamspace.
  • Jira rejects the issue because a field is required. Some Jira projects require additional fields on create, so ask your Jira admin to review the project configuration or validators.
  • The share fails with a permission error such as 403. Make sure you have permission to create issues in the target Jira project.
  • The issue lands in the wrong place or does not match the expected type. Recheck the saved Base URL, Project ID, and Issue Type in the Jira connection.
  • Jira sharing works for one project but not another. Create separate Jira connections per project and issue type instead of reusing one configuration for different workflows.

FAQ​

Q: What settings does NEXT store in a Jira connection?​

Each Jira connection stores the Jira base URL, project ID, and issue type used when the issue is created.

Q: Can I create different Jira targets for different workflows?​

Yes. Create multiple Jira connections, for example one for bugs and one for stories, then choose the right one when you share.

Q: Why does Jira reject the issue?​

The most common causes are a wrong project ID, a wrong issue type, missing create permissions, or Jira-required fields that are not available through the connection.

Only people who already have permission to view that item in NEXT.

Q: Does NEXT upload the video file to Jira?​

No. NEXT creates the Jira issue and links back to the source in NEXT.