What to expect
This integration allows you to generate Jira tickets directly inside Contentsquare, so you can:
- Identify issues related to errors and session replays, and then create tickets.
- Share their full context with developers and your most impactful errors with your entire team.
- View errors you've already created tickets for and check their current statuses to prioritize issues more efficiently.
- Navigate directly from the error to the related Jira ticket.
- Avoid creating several tickets for the same issue and optimize your workflow.
Implementation
There are two ways to install the Jira integration:
- Install the integration on the fly when clicking "Create Jira issue".
- Or install it via the Integration catalog:
- Click on the puzzle icon in the top-right corner of your screen.
- Search 'Jira' and click 'See details'.
- Read the integration details, and click 'Connect'.
- Authorize the access to your Jira account and wait until the authentication is complete.
Note
This integration is user-based, meaning other users on this project will need to install it as well. All Jira tickets created will be created by the specified Jira user. Available projects on Jira will depend on each user's permission.
How to create a ticket
Creating a ticket in Session Replay
Note
The creation of Jira tickets can only be carried out by Admin, Expert or Analyst user roles.
On a specific session recording, click 'Share' and then in the pop-up that opens, click 'Create Jira issue' and follow the on-screen instructions.
Creating a ticket in Error Analysis
- Click on the '>' button to open the error side panel and click the 'Create Jira issue' button.
- Proceed to complete the form details. You can edit the title and description of the ticket to add information. Please note: The form details displayed are based on the 'Issue type' template configured in Jira.
Select 'Create', and you're done!
What information is used by Jira?
The following information (pulled from the Error module) will pre-populate in the description field:
| Error type (Summary) |
| Group ID |
| Scriptlocation |
| Links to Session Replay with the error |
| Error dimensions |
| Link to Impact Quantification |
| AI Error summary |
What happens for required but not supported fields?
If you have information from Jira fields that are required but not supported (see the comprehensive list of unsupported fields below), you will see this notification, and the 'Create' button will be locked as shown below:
The Jira integration does not support projects that have the following fields:
- 'Assignee'
- 'Attachment'
- 'Duedate'
- 'Environment'
- 'fixVersions'
- 'Issuelinks'
- 'Parent'
- 'Security'
- 'Subtasks'
- 'Timeoriginalestimate'
- 'Labels'
As well as the following field types:
| Field Type | Field custom schema |
| Date time | com.atlassian.jira.plugin.system.customfieldtypes:datetime |
| Asset field | com.atlassian.servicedesk.assets-plugin:assetfield |
| Text field read only | com.atlassian.jira.plugin.system.customfieldtypes:readonlyfield |
| Versions | com.atlassian.jira.plugin.system.customfieldtypes:multiversion |
Good to know
Once you have created the ticket, you can't edit the details in Error Analysis.
View the details of an existing Jira ticket
- In Error detail, click on 'View Jira issue'.
- In the 'Issues created for this Error' section of the Jira modal, click on the issue link to open up the ticket details directly in Jira.
FAQ
Can I reverse the Jira status in Error Analysis?
The Jira status is not reversible. Once a ticket is sent to Jira, the status will remain.
Can I edit the ticket in Error Analysis?
Once the ticket is sent, it can only be edited directly in Jira.
Is Jira server supported?
No, only Jira Cloud is supported at the moment.