Noibu's Jira Integration creates a direct path between issues in Noibu and tickets in Jira. After triaging an issue, you can sync the issue to Jira to create a corresponding ticket with all the information your developers need to solve the issue. But what if you already have a Jira ticket that documents a known bug, and you want to find the corresponding issue in Noibu? Unfortunately, the integration is unidirectional, but through Noibu's advanced filtering and search capabilities, you can work backwards from the Jira ticket to find a matching issue in Noibu, and sync your debugging efforts on both fronts.
You can link a backlog ticket to a Noibu issue through one of two methods:
Method 1: Search by Error Message
If the Jira ticket includes an error message, you can search through the Issues table for an issue with matching error text. Some error messages are so general that a search may pull up multiple issues. To ensure you find the correct issue, we recommend collecting as much information about the known bug as possible, like the date and time it was last observed, and using this information to apply additional filters.
- Open the Issues table, and click into the All Issues view.
- Enter the error message in the Search bar. If the error message is long, enter a segment that identifies a function, filename, or another specific attribute. This filters the table by issues with matching names or error signatures.
- If the search pulls multiple results, add additional filters like the Last Seen or Created date, the page type on which the issue typically occurs, or another detail.
Method 2: Find Relevant Sessions
If the Jira ticket does not include an error message, or the message is too generic to pull a specific issue in Noibu, use details in the ticket to find a session where the issue occurred. Noibu's Sessions page records every unique shopper session on your eCommerce website, and if you can find an example of a shopper experiencing the issue in a session, you can open the issue's details to aid your investigation. This process is simple if the ticket includes identifying information such as:
- A shopper's IP address
- A store identifier, like a customer ID, session ID, or anonymized user ID. Noibu does not track these attributes by default, but you can configure the NoibuJS SDK to track up to 10 custom attributes in session recordings.
Finding a relevant session without a unique identifier can be tricky, but it's not impossible. Scour the ticket for details that might help you uncover a shopper session where the issue occurs. Helpful details include:
- The date and time the issue occurred
- The shopper's browser and operating system
- The URL on which the shopper encountered the issue.
- The last thing the shopper clicked before the issue occurred, if applicable
- The last funnel step the shopper made it to before their progress was blocked, if applicable
With as much detail as possible, apply filters in the Sessions table to pull sessions that match the conditions documented in the ticket.
From here, watch session recordings, and examine the issues listed in the Session Timeline. Often, multiple issues surface during a single session, so this process takes time and patience.
Once you find an issue that matches the bug reported in your Jira backlog, create a link between the issue and the ticket. To do so, open the Manage tab, click Sync Issue with Jira, and enter the existing ticket's Jira Issue ID in th field provided.