If you work in software development, you know that bugs happen. Managing and prioritizing bugs is an important part of your team’s workflow!
What is a Bugs Queue?
A bugs queue is a great way to list and prioritize any and all bugs that occur when a flaw appears within your software. Once you identify bugs, you can efficiently manage and prioritize them via a bugs queue within monday.com!
Who uses it and why?
A bugs queue can be used by multiple teams across your organisation including your development, customer success, sales, and product teams. Let’s start building out your board!
We’ve provided a 4 step guide below to show you how to create a bugs queue. Let's get started! 🎉
Choose a template
Check out the Software Development section on the Templates list when creating a new board. We recommend the Bugs Queue template.
You can also check out this monday.com story that we've created especially for you, and add it directly to your board.
Customize your board
On our Bugs Queue board, we've divided each group by completion. We work in terms of prioritizing new bugs, tracking those that are currently in progress, and also keeping track of closed bugs where a fix has been successfully deployed!
In this case, we prioritized by these categories – though you could also group them by time frame, priority, or assigned team members. You can customize it to make it work well for you and your team!
Once you have set up your groups, you can start adding your items. An item can be each individual bug that you encounter and need to fix.
Columns help ensure that we have all the relevant information in one place for each bug and to ensure that we're managing each bug based on priority. We also want to make sure we know who is assigned to fix the bug. We have over 20 different columns allowing you to customize your board the way you want!
People Column: There are going to be multiple team members involved along the way - the reporter and the assigned team member on the development team. The people column allows you to assign each team member, making it clear who's responsible for what. Adding multiple People columns allows the developer to reach out to the reporter in case of questions.
Date Column: In order to track and prioritize bugs, we have added a Bug Submission date to understand when the bug is first reported.
Status Column: Each post has multiple areas that will determine who we assign each bug to. For example, if the customer impact is critical we want to assign the bug to someone who has the capacity to work on this as soon as possible. By adding status columns and customizing the labels, we're able to do more than just track status, but also can track customer impact and the source of the bug.
Add a view
Views allow you to see certain pieces of information from your board in another way - always visual and easy to understand. In our case, the status type is extremely important since we want to prioritize Critical and Major bugs to help our users! So, on our Bugs Queue board, we've added the Kanban view.
From this view, you can move posts if the impact of a bug changes and view in a visual way, different from how you can track items within your board. You can continue to add items to certain areas or move a bug from one status to another.
Automate for efficiency
Organizing your board and priorities is important, but why should this be time-consuming? With our automations center you can more efficiently manage your bugs queue!
When a bug has been fixed we want to move from the New or In Progress group to the Completed group. Instead of manually dragging and dropping the item we can use a status change automation. When you click Add to Board you will be prompted to fill out the below recipe:
I want all bugs with the status Fixed to moved to the Closed group so I will click through the recipe to show the following:
Now every time our team fixes a bug the item will automatically move to the closed group.
If you have any questions, please reach out to our team by using our contact form. We're available 24/7 and happy to help!