Documentation

Bugs

Track defects from detection through to resolution.

Suggest Edits

In Atono, bugs are tracked separately from stories to help your team focus on resolving issues efficiently. This distinction allows bugs to have their own workflow, tailored for quick assessment and resolution, so you can keep your product running smoothly while maintaining progress on new features.

Create a bug

Creating bugs in Atono helps track and resolve issues efficiently. Here’s how to get started with a new bug:

  1. In the sidebar, click or hover over Create new.
  2. From the menu, select Bug.
    • This opens a draft version of your bug that partially overlays your screen, allowing you to navigate to other pages in the Atono web interface while working on your draft.
    • If you minimize the draft window, the sidebar displays a badge on 'Create new' to indicate you have an unsaved draft. You'll need to open and save the draft before you can create another new item.
    • Even if you refresh your browser or sign out, your draft will be there when you return.
  3. Provide a descriptive title for the bug.
  4. As a best practice, use the suggested template to provide information about the bug using the following sections of the bug report:
    • Summary: Provide a concise, one-sentence explanation of the problem. Make sure it clearly states what the bug is, focusing on the issue rather than potential causes. For example: 'Unable to save changes to a user's profile after changing their role.'
    • Reproduction Steps: Describe step-by-step instructions to reproduce the bug. Be as detailed as possible to ensure that anyone, even without prior context, can follow the steps and encounter the same issue. For example: '1. Navigate to a user's profile. 2. Modify their assigned role. 3. Click the 'Save' button.'
    • Expected Behavior: Explain what should happen when the bug is not present. This helps highlight the difference between the intended function and the bug. For example: 'The changes to the role should save, and the user should see a confirmation toast.'
    • Actual Behavior: Describe what is happening instead of the expected behavior. Be specific about any error messages, glitches, or system behaviors observed. For example: 'The 'Save' button becomes unresponsive, and the changes are not saved. No error message appears.'
  5. Assign the story to a workflow step (like 'To do'), a user, and a team backlog (you can update these later).
  6. Optionally, select the Affected environments where you've observed the bug.
  7. Optionally, triage the bug by assigning it a risk rating and adding it to a team's backlog.

⚠️

Recommended best practice

Skip this step for the bug to appear in Bug triage, where the team responsible for triaging bugs can assess its risk rating compared to other reported bugs, or request more information if required.

  1. Click Create to save the bug, or click X to discard it.
    1. If the bug is assigned to an 'In progress' workflow step, you'll be prompted to set the date and time work on the bug began for more accurate cycle time tracking.

If you created the bug on a specific team's backlog, it will appear at the bottom of the step in the 'To do' category.

Change the reporter

When you create a bug, you are listed as the reporter. To modify this, such as if someone else reported the bug and you're the one making the ticket, click your name next to reporter in the sidebar and select a different user.

You will still be listed as the person who created the bug in the Activities list and there will be an entry that you changed the reporter.

Assign a bug to a user

Assigning a bug to a user ensures clear ownership, so everyone knows who’s responsible for resolving the issue and progress can be tracked.

  1. In the bug details panel, click Assign.
  2. Search for or select a user.

To change the assignee or unassign the bug, click the name of the current assignee and select a different user, or choose No assignee.

Add a bug to a team backlog

Assigning a bug to a team's backlog in Atono helps ensure issues are properly prioritized and addressed within the team's workflow, so critical problems don’t get overlooked.

  1. In the bug details panel, click Add to team backlog.
  2. Search or select a team.

You can change the team backlog a bug is assigned to or unassign it to move it to Bug triage.

  1. Click the name of the current team and select a different team, or select Unassigned to team.
  2. In the confirmation dialog, confirm by clicking Change backlog or Unassign from team, depending on your choice in the previous step.
    • If you select to change backlogs, the bug is removed from its position in the current team's backlog (for example, 'In progress') and moved it to the bottom of the 'To do' workflow step in the new backlog.
    • If you select to unassign the bug from a team, it is moved to the Reported bugs section of Bug triage. Bugs in this section are ordered from oldest (first) to newest (last) date reported.

Update a bug's risk rating

Although it's a best practice to let your organization's triage team determine a bug's risk rating in Bug triage, there are times where someone may need to update the risk rating value after it's been triaged. You can do this directly from the bug.

  1. Open the bug from the assigned team's backlog.
  2. At the top of the bug, next to its title, click the risk rating.
  3. Select a new probability and impact value, then click Save.

If you change the probability or impact value to Not selected, the bug will be added to the Reported bugs section of Bug triage.

Reference bugs

In Atono, copying a bug’s URL lets your team quickly access the exact issue without wasting time, ensuring everyone is aligned and can collaborate efficiently.

Copy a bug ID

Easily copy a bug's ID (for example, "BUG-27") to paste into other tickets or communications.

In the bug header, next to the bug ID, click the Copy ID icon. The bug ID is now saved to your clipboard, ready to paste elsewhere.

Copy a bug URL

Copying a bug URL allows team members to quickly share and access specific bugs, facilitating efficient collaboration and communication within Atono.

In the bug header, click the Copy URL icon. The URL to the bug is now saved to your clipboard.

Link items

Linking related items to a bug helps you highlight dependencies, document related issues, and provide additional context for resolution. Visible connections between items makes it easier to address blockers and prioritize fixes. For more on linking items, see Linked items.

Attach files

Attach files to your bugs to provide context, screenshots, or logs that help diagnose and resolve issues faster. Keeping all necessary information together ensures the team can troubleshoot efficiently. For more on how to add and manage attachments, see Attachments.

Add comments

Comments on bugs help your team share insights, ask questions, or provide updates on resolving issues. Centralizing discussions in the bug keeps everyone informed and speeds up troubleshooting. For more on using comments, see Comments.

Bug activities

Every bug includes an Activities section with a detailed record of all actions related to the bug, from changes in assignees and team backlog to updates to the bug description and the reporter. This history helps your team track progress and decisions over time, ensuring transparency and alignment.

For more details on how to sort, filter, and manage activities, see Activities.

Delete a bug

You might want to delete a bug when it's no longer valid, was reported by mistake, or has been resolved through other changes in the project. However, resolved bugs are often worth keeping around for reference. They help your team track the history of issues, understand past fixes, and provide context for diagnosing future problems, especially if similar issues resurface.

  1. In the bug header, click the ellipses (...) icon.
  2. From the menu, select Delete bug.
  3. In the deletion dialog, confirm by clicking Delete, or click X to cancel.

Bug identifiers in Atono are assigned sequentially. If you delete a bug, Atono won’t reuse its number unless it’s the next one in line. For example, if your workspace has 47 bugs and you delete BUG-7, the next story created will be BUG-48. If you delete BUG-47, the next story created will use that number. This keeps your bugs numbers in a logical sequence.

Updated 8 days ago