Available for the following Plan types:
FullStory for Mobile Apps
Available to the following User roles:
FullStory's integration with Jira makes it easy to create a new Jira ticket when you notice a bug or issue in a customer's session in FullStory. We'll automatically send all the details we have about the customer's session (including a link to the playback and the customer's URL, IP address, UserAgent, and Viewport details), making it faster and easier to understand and reproduce the customer's experience and start solving the problem.
Setting up the integration
- Log in to FullStory and go to Settings > Integrations > Manage
Click “Add” next to the Jira integration, then “Authorize” to set up the new integration.
Sign into Jira with your Atlassian credentials. Once signed in successfully, you’ll be returned to the FullStory integrations page.
- Set the Project and Issue Type. When you share a FullStory note to Jira it will be for the project and as the issue type you indicate here. Then click Done.
Note: If you're missing some Projects in the dropdown, scroll to the end of this article to see how to troubleshoot.
- Now that you've enabled and set up the integration, when you make a note on a FullStory session, you'll see the option to share that note to Jira.
- When you select Jira in the dropdown list, you'll see a new window where you can customize the content used to create the ticket. We'll automatically use your note text as the summary and we'll add all the session details to the description section of the ticket. You'll also need to set any required fields as you're creating the Jira ticket.
- Click Send and the ticket will be created in Jira. Look for the success notification in the bottom right hand corner.
- You can then access the Jira ticket under the Notes section. Simply click the Jira link, next to the "Send to:" callout:
- Then click here in the notification in the bottom right of the screen to go directly to the ticket in Jira:
Here is an example of what you will see in Jira:
Updating your Default Settings
By default, all of your Jira notes will be sent to the Project you indicate and be set as the Issue Type you indicate during setup. You can change the default settings any time you need from FullStory settings.
- Navigate to Settings > Integrations > Manage.
- Next to Jira, click Manage.
- Use the pop-out menu to disable the integration or change the project or issue type.
- The FullStory Jira integration does not attempt to connect FullStory users to their corresponding Jira user permissions. The integration connects to Jira with admin-like permissions. This means FullStory users who might not normally have Jira admin permissions to create certain issue types in certain project will be able to do so via the FullStory "send note" functionality. By default, this functionality only exists for the one project and issue type that is configured in the Jira integration, on our integration settings page. If however, the ability to change the Jira project and issue type is enabled during the "send note" process, FullStory users will be allowed to create any issue type in any project, thereby increasing the risk that they might be bypassing Jira security configurations.
- The project I want doesn't appear as an option when configuring the integration (step 4 above)
Often, this is a permissions issue. The FullStory integration must have "create issues" permissions on any project that you want to use. To view or edit project-level permissions, go to [cog in the upper right] → Projects tab → [click on a project] → Permissions and then scroll down to "create issues".
For Jira On-Prem users, follow the below instructions:
- Determine desired Event in FullStory as Webhook Trigger
- Use Jira Automation or similar middleware to create an HTTP endpoint to be used with FullStory Webhooks.
- Create a new webhook in FullStory.
- Add HTTP endpoint created earlier.
- Select Event in webhook to use as trigger/firing condition.
- Enter a Secret (if required) and provide to customer as handshake confirmation that the HTTP request is coming from FullStory.
- If endpoint service requires Basic or Bearer token auth then that value should be entered in the Secret field.
- Save webhook.
- Conduct test event(s) to validate webhook is firing as expected and endpoint is returning a 200 Success response.