Skip to main content

Manage Issues sidebar

The Manage Issue sidebar on the Issue Overview and Technical Details tabs makes it easy to prioritize and action an issue. From this panel a product owner can easily specify the issue’s urgency, assign the issue to a developer for resolution, pin it for future reference, and even sync it to Jira.

 

Pinning an Issue

Pinning an impactful issue highlights it for easy reference in the future. Any Pinned issue appears in the Pinned issues tab of the Issues page.  You should pin an issue if you find evidence that it's impactful to the shoppers experience to ensure it isn’t lost in the shuffle as you investigate other issues. Click the ‘Pin’ icon to pin an issue. 

 

Syncing an Issue to Jira

Noibu's integration with Jira 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. Before you can sync an issue with Jira, you must connect the Jira Integration.

Click the ‘Jira’ icon to sync an issue to Jira. This brings up a modal to enter details about the issue.

 

Select a Jira project and enter a brief description in the field provided. If applicable, enter an existing Jira Issue ID in the field to link an existing Jira ticket to a Noibu issue. Learn more about Linking Backlog Items to Noibu Issues. Click Sync Issue with Jira to connect the issue from Noibu to Jira.

 

Sharing a link to an Issue

Sometimes it might be necessary to share details of an issue with a third party who doesn't have access to Noibu. For example, a third-party issue may need to be shared externally to allow them to diagnose and resolve from their end.

Every issue includes a button to generate a link to share a subset of information to external parties.

A shareable link provides general details about the issue, as well as a stack trace and any pinned session recordings to help external parties resolve the issue. 

Note: A third party accessing an issue via a shareable link can only see Pinned Sessions. Be sure to pin any relevant sessions before sharing the link with your provider.



 

Issue Management fields

Issue Management fields help you track your team’s progress on an issue. 

Product owners often populate these fields as part of their triage process, while developers use these fields to log updates as they work towards a resolution.

  • Labels: use custom labels to easily group similar issues. Learn more about configuring labels. 
  • Urgency: Set the issue's urgency as part of the triage process. An issue's urgency can be Unset, High, Medium, or Low.
  • Assignee: If you decide to action the bug fix, assign the task to a team member.
  • Status: used to track its progress through triaging to debugging to resolution. An issue may have one of five statuses. Update the issue's state manually as you progress:
    • New: An issue state. Indicates the issue has been created, but nobody has looked at it yet.
    • Open: An issue state. Indicates the issue is in the early stages of investigation. At least one employee has had eyes on the issue, and the issue will be triaged soon.
    • In Progress: An issue state. Indicates the issue is being actively worked on by a developer. We recommend using this state after assigning the issue to a developer.
    • Closed Ignore: An issue state. Indicates the issue will not be solved. This state closes the issue, and stops Noibu from sending alerts about the issue, which may be troublesome if the issue causes problems in the future. Use this state sparingly.
    • Closed Fixed: An issue state. Indicates the issue has been resolved and closed, but Noibu will alert you if the issue causes further problems.
  • Description: A short description of the issue. Populate this field after investigating the problem in the triaging stage, and before assigning the issue to a developer.

Activity

The Activity section keeps a running log of updates to the issue, including state changes, pinned sessions, assignee changes, and more. You can leave a comment to share information and engage in a dialogue with other users. This is useful in cases where multiple developers work on the same issue, or a developer reports to a product owner. 

Articles in this section