Investigating and triaging Uncategorized errors on the Issues page may seem like a challenging task. To uncover priority and determine which errors to action to developers, follow the steps below.
- Investigate the errors from highest to lowest priority as ordered in the Priority Issues view. This ensures you examine the most impactful errors first.
- Note: Sort the table by Resolvability to ensure you action high-impact fixes with a resolution history.
[issues-priority-view]
- Note: Sort the table by Resolvability to ensure you action high-impact fixes with a resolution history.
- Check each issue's Correlated Issues tab. Issues rarely occur in a vacuum, and you can often trace two or more issues back to the same root cause, or gain context for one issue by examining another. Furthermore, sometimes one issue is caused by another, and fixing one may fully or partially resolve the other. Therefore, resolving an issue with several correlated issues may have a ripple effect.
[correlated-issues] - Open each error's Issue Profile and click into the Sessions tab. Watch a few videos from sessions where the error occurred. If you cannot see the user impact after watching 4-5 videos, move on to the next error.
[issue-sessions-overview]
- Note: Watch for subtle impacts that disrupt your user’s journey. Errors with a clear StackTrace and significant drop in conversion should be prioritized, even if there is no clear video.
- Note: Watch for subtle impacts that disrupt your user’s journey. Errors with a clear StackTrace and significant drop in conversion should be prioritized, even if there is no clear video.
- If you find a video that captures the user impact, Pin the Session(s) to review later. Be sure to leave a helpful comment.
[issue-pinned-sessions] - Open the Overview tab, mark the error’s Impact as User Impacting, and click Save. Now, the error will appear at the top of the funnel.
[issue-management] - Action the bug fix. This includes assigning the issue to a developer, setting a priority, and entering a brief description.
- Note: If your dev team uses Jira, we recommend setting up the Jira Integration.
- Note: If your dev team uses Jira, we recommend setting up the Jira Integration.
- Fix the error! While each error has unique properties and challenges, we've assembled some best practices, strategies, and processes to help developers through the Debugging workflow.
If you determine that an error does not significantly impact your users, mark the error’s state as Closed Ignore or Benign. This removes the error from the Priority Issues view, but you can still access the error from the All Issues view.
For more information, feel free to contact us at support@noibu.com.