On Bug Triaging

I thought this was a very interesting article on triaging bugs. It uses 3 metrics:
* Type: What type of bug is this? For example is it a crashing issue, a problem with localization or a matter of visual polish?
* Likelihood: How likely are users to experience the bug? For example, does everyone run into the issue or do only a few users run into it?
* Priority: Of the people who experience the bug, how badly does it affect their experience with the product?

Each metric is assigned a number, which when multiplied together produces a number representing "user pain", that is, how much pain it causes users. Bugs can then be sorted by this number, and you fix bugs from the top.

It's a shame bugzilla doesn't really offer much flexibility for stuff like this. I'm not saying this is the best way to prioritize bugs, but it would be nice to have some ability to try out different methodologies.

Comments

Post a Comment

Popular posts from this blog

Introducing Pinta

Image
Over the holiday break, I stumbled upon this article from OSNews stating that there was a need for something like Paint.NET for Gtk. Having some experience with porting Paint.NET to Mono Winforms before, I knew that that was a massive task. But it still got me curious about Cairo and creating a layered canvas, since I had never played with Cairo or Gtk. After playing around for a few hours, I actually had a working paintbrush and canvas. Intrigued by my success, I played around with it for a few more days. By the end of the week I had a nifty little paint program with a few features. Now, a month later, it's time to open my little project up to the world: Pinta . Pinta is a clone of Paint.NET. It already has a small, but hopefully useful, set of features like multiple layers and infinite levels of Undo/Redo. I hope to implement the same feature set as Paint.NET. Currently there are several tools missing, as well as adjustments like brightness/contrast and levels and Pain
Read more

Hack Week 3

Image
As part of this year's Google Summer of Code, there were two projects that got chosen that were on my personal 'to-do' list. I was happy these projects got chosen because frankly, my to-do list is not getting shorter nor are the days getting longer. One of these is Ed Ropple's "Cloverleaf", which is an add-in to Visual Studio designed to facilitate writing and testing applications in Mono. We decided on the following features: - Test in Mono: Clicking this would run the current solution/project on the Mono runtime on Windows. - Scan with MoMA/Gendarme: Clicking this would run MoMA or Gendarme (which can run MoMA) on the solution/project. - Test on Linux: Clicking this would take the solution/project output and copy it to a Linux machine or virtual machine, and automatically start it. Ed did some great work over the summer, so for my Hack Week project I started polishing and packaging his code so we could get it into people's hands. Unfortunately, I
Read more

Mono in Visual Studio 2010

Image
One cool new feature in Visual Studio 2010 is enhanced Multi Targeting . Presumably, its all about allowing developers to target both the 2.0 and 4.0 runtimes from VS2010, but what it really means is you can easily target Mono from within Visual Studio 2010. Like this: To enable this, you need to unzip this file to: C:\Program Files\Reference Assemblies\Microsoft\Framework\.NETFramework\v3.5\Profile Once you do that, you can take your .NET project: Go to project properties and switch it to the Mono 2.4 Profile: Now it will compile using Mono's assemblies, and will flag methods that Mono does not contain, like thus: This also works for Intellisense: And Object Browser: We are very excited about this feature, which should make it easy for people to ensure they are staying compatible with the Mono subset of the .NET framework without leaving Visual Studio. Once VS2010 is released, we will hopefully release the profile packs as we release each Mono version!
Read more