The Bug triage page in Atono helps your triage team prioritize and address the bugs that pose the highest risk to your business. It provides a separate space from your other backlog items, where your team can review, assess, and take action on bugs reported through the Atono web interface or the Atono Chrome extension.

To access this page, click Bug triage in the side menu.

Triage a bug

A bug is considered triaged when it has a risk rating and is assigned to a team's backlog. Until both of these actions are completed, the bug remains in the triage list.

A bug's risk rating is automatically calculated once you set values for both probability and impact.

1. In the Reported bugs section, click the bug you want to triage. This opens in the bug in a panel next to the triage list.
2. Click Triage.
3. Select a probability and impact value to calculate the risk rating. The risk rating is determined by multiplying the probability and impact values, with both ranging from 1 (lowest) to 5 (highest). The result will be a risk rating between 1 and 25 (where 25 is the highest risk).
   • Probability: The chance this bug will be experienced by a customer, compared to other bugs.
     • 1 - Impossible
     • 2 - Unlikely
     • 3 - Possible
     • 4 - Probable
     • 5 - Certain
   • Impact: The severity of this bug's impact on a customer, compared to other bugs.
     • 1 - Negligible
     • 2 - Minor
     • 3 - Medium
     • 4 - High
     • 5 - Severe
4. Assign the bug to a team's backlog by clicking Add to team backlog and searching for or selecting a team.
   • If you add the bug to a team backlog and save before you complete the risk rating, the bug will appear in both Bug triage an on the assigned team's backlog.
5. Click Finish.
   • Once completed, the bug is removed from Bug triage and added to the bottom of 'To do' category in the assigned team's backlog.

⚠️

Assigning bugs to private team backlogs

If you assign a bug to a private team's backlog, only authorized users will be able to access it. If you're not a member of that private team, you will lose access to the bug. As a best practice, consider setting the risk rating before assigning a bug to a private team.

Request more info

If you don't have enough information to triage a bug, you can request more details from the person who reported it. Adding Comments to specific parts of the bug description or bug itself helps the reporter understand your questions.

1. When viewing a bug in Bug triage, click More info required.
   • The bug is moved to the More info required section and is automatically assigned to the bug reporter.

Reject a bug

If you decide a bug is no longer relevant or won’t be addressed, you can reject it.

1. When viewing a bug in Bug triage, click Reject.
   • The bug is moved to the Won't do section of the Bug triage.

Identify 'old' bugs

Identifying old bugs helps your team prevent overlooked issues that could impact product stability or user experience. Keeping track of bugs that have been in triage for an extended period ensures your team can take timely action before problems escalate.

Atono provides two ways to help you identify 'old' bugs—those that have been in triage for more than seven consecutive days during their current time in triage (since bugs can move in and out of triage):

• The Bug triage label in the side menu displays a badge when there are old bugs.
• Individual bugs in the Reported bugs or More info required sections are marked with a red clock icon when they've been there for more than seven days.