With FullStory + Jira Cloud, each time you receive a ticket through support or any other channel, you’ll have the power of FullStory to fill you in on the details. I can’t reproduce the bug is no longer a thing when you can see every user action and DOM state leading up to the critical moment, review the JavaScript console in sync with the playback, easily correlate problems to your server logs, and even get the relevant customer information such as browser, OS, user-agent, display size, and more.



Get the most out of FullStory + Jira Cloud


How it Works

FullStory's integration with Jira Cloud 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.




1. Log in to the FullStory account for which you want to install Jira Cloud.

2. Log in to your Jira Cloud Instance

3. From the Jira homepage, go to Apps > Manage your apps > Find new apps.

4. In the Atlassian Marketplace for Jira page, search for FullStory and click Install on the FullStory integration.

5. Click Accept & install to add the FullStory for Jira add-on to your Jira instance.

6. Once the add-on is installed, click Get Started to set up the configuration.

7. Click Connect to finish the configuration within FullStory.

8. Set the Project and Issue Type. When you share a FullStory note to Jira Cloud it will be for the project and as the issue type you indicate here. (You can change these defaults later in FullStory settings). Then click Save Configuration. NOTE: If you're missing some Projects in the dropdown, scroll to the end of this article to see how to troubleshoot.

9. Now that you've enabled and set up the add-on, when you make a note on a FullStory session, you'll see the option to share that note to Jira Cloud.

10. When you click SEND TO: Jira, 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.

11. Click Send and the ticket will be created in Jira Cloud. Look for the success notification in the bottom right hand corner.

12. You can click on the note link in this pop-up notification to view the newly created ticket in Jira Cloud. You can find this link again by clicking on the 'Jira Cloud' link in your FullStory playback note again.

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 & API Keys

• Next to Jira, click View.

• Use the pop-out menu to disable the integration or change the issue or project type.

• The FullStory Jira Cloud integration does not attempt to connect FullStory users to their corresponding Jira user permissions. The integration connects to your Jira Cloud instance 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 Cloud integration, on our integration settings page. If however, the ability to change 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 add-on (step 7 above)

Often, this is a permissions issue. The FullStory add-on must have "create issues" permissions on any project that you want to use. Typically, this permission is granted by default when you first install the add-on, but depending on your Jira configuration this may not be the case.  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".



Built by: FullStory

Setup: Turnkey 

Support: support@fullstory.com 

Version: 1.0