If it’s your job to deal with application lifecycle management, you’re already well aware of how important bug tracking actually is. Even though most people know of its importance, it’s still strongly underused by development and quality teams – what good is it to have a great bug tracking tool if most of its functionalities are not being applied to good use?
Don’t worry too much about it, though, this neglect can be remedied through the implementation of a few basic ground rules and best practices to your bug tracking process.
Bug Tracking fundamentals
It makes no difference whether you choose to track your bugs using a spreadsheet, pencil and paper or a bug tracking tool – though I’d strongly recommend you to use Pipefy’s Bug Tracking Template – the basic fundamentals will always be the same:
To report and track a bug, certain information will need to be provided and, to ensure you’ll actually have all the information you need, you have to establish a couple of rules. If you’re working with Pipefy, for example, it would be simple to create a very detailed start form on your bug tracking Pipe, specifying the mandatory fields and adding instructions on how to provide the information on each and every field.
Using Pipefy to track your bugs will ensure your process will be simple enough so that people can actually use it on a daily basis without oversimplifying it and leaving essential information out of the table.
After a bug has been duly reported, with all the necessary information, the next step is prioritising and establishing when it’ll be fixed. You can determine the priority of the defect according to a sum of factors, but it’s often done by the severity of the problem and direct user impact.
Pipefy offers you the possibility to label each of your cards, identifying the priority of each one by a coloured stripe on the top of the card. You can edit and create labels on your Bug Tracking Pipe in order to make it suit your needs.
After a bug has been reported, there needs to be an open and accessible channel to allow for constructive communication between the person who reported the bug and the one responsible for correcting it – assuming they’re not the same, cause that sounds a little weird.
Using Pipefy you can add comments to your cards with mentions to the people on your team – assuming they’re members of the Pipe – making sure they’ll be notified there’s a new comment regarding a specific bug.
In order to test and verify the correction of the bug, the person in charge needs to be able to reproduce the exact environment and circumstances it originally happened. Also, some defects only exist in very specific situations so, in order to make sure the testing is really thorough, it’s necessary to identify and test all possible element combinations. It’s possible to fix a bug that can’t be reproduced, though it’s a lot more difficult and time-consuming.
Stay tuned for tomorrow’s post, we’ll keep on talking about bug tracking and present you with a few best practices to make it easier for you to structure your bug tracking process.
Track your bugs with Pipefy:
If you’re looking for a simple and intuitive way to start tracking your bugs, try Pipefy! We help companies keep organised and more productive by running their processes and day-by-day routines on an easy and intuitive tool.
Pipefy’s Bug Tracking template offers you with the structure you need to report, prioritise and track all your bugs in a centralised, easy to use platform. It keeps all your reported bugs organized and helps you classify and prioritize them.
It comes with a detailed start form to allow your team to properly report all the details of the bug: the time it was reported, it’s severity, where it happened and a complete method to evaluate its impacts on the user experience and your business goals.