Triaging issues – user pain, custom fields and more
So, the next technology preview of version 3 is dragging out because of our developers being busy with other things. This would be a good time to talk a bit about one of the features implemented in this upcoming preview release: issue triaging.
Triaging issues is a common task to do when working with a bug tracking system. The bug genie has never had a real way of handling triaging, although you can always use the built-in issue types, data types and editable data type values. So far, this has worked out very well, but for version 3, we wanted to take it a step further. Acknowledging that your workflow might not fit perfectly with the set of data types and values provided by default, we’ve added two new major features in version 3.
Custom issue fields
Custom issue fields is something that has been asked about for quite some time, even back in the v1.x days, through v2, and is finally being addressed in V3. Using custom fields lets you set any kind of information on any kind of issue/ticket, and makes the bug genie a lot more powerful and customizable for non-default workflows. Implemented almost the same way as editing data type values for built-in data types (status, priority, resolution, etc), adding customized data types and values is a breeze. Just as with built-in data type values in v3, you can also combine them with issue types to set visible fields on different types, and build custom reporting forms with them. You want to have “Operating System” as a required field with a drop-down select list during reporting – no problem!
Custom issue fields in v3 are first-class citizens, and we want to keep it that way.
Triaging issues with “User pain”
After reading a post on lostgarden.com about the “user pain” concept, it was quite obvious that this was a good way to start adding triaging features to version 3. Implemented in the upcoming preview release, we’ve added all the features mentioned in the blog post, and it’s looking better than ever. Scoring and triaging bug reports works as a charm. We’ll let you try it out when releasing the next preview release of version 3.
Version 3 is scheduled for release first half 2010, with regular preview releases up to the first alpha release in April, 2010.