We need a way to order bugs in a sprint by some kind of "importance" factor so that it's clearer which bugs need to get done earlier in the sprint.
SUMO was using the Bugzilla Priority field for this, but now that it takes forever to pull that data into scrumbugz and because scrumbugz is now the authority for sprint-related data, it makes sense to have scrumbugz manage the ordering.
A bucket list would work fine for us. Each bug would go in either the "first", "second", "third" or "blocked" bucket. We'd make the "blocked" bucket computed. People could otherwise assign a bug to a bucket. Then we have a sorted view of the bugs that show all the bugs in the "first" bucket first, the "second" bucket second, ... and the "blocked" bucket last. Or something like that.
The use cases I want to solve here are three fold:
a developer looks at the sprint to see what they should work on next and would like to work on the next most important bug
a pro(ject|duct) manager wants to denote bugs they need landed earlier in the sprint
if there are bugs in the sprint that are blocked by other bugs in the sprint, then we can denote that the blocker bugs get worked on earlier
The last could probably be done in other ways. I know @pmclanahan was thinking of adding an on-hover thing to the "blocked" tag but it'd help to have an ordering mechanism for it, too.
We need a way to order bugs in a sprint by some kind of "importance" factor so that it's clearer which bugs need to get done earlier in the sprint.
SUMO was using the Bugzilla Priority field for this, but now that it takes forever to pull that data into scrumbugz and because scrumbugz is now the authority for sprint-related data, it makes sense to have scrumbugz manage the ordering.
A bucket list would work fine for us. Each bug would go in either the "first", "second", "third" or "blocked" bucket. We'd make the "blocked" bucket computed. People could otherwise assign a bug to a bucket. Then we have a sorted view of the bugs that show all the bugs in the "first" bucket first, the "second" bucket second, ... and the "blocked" bucket last. Or something like that.
The use cases I want to solve here are three fold:
The last could probably be done in other ways. I know @pmclanahan was thinking of adding an on-hover thing to the "blocked" tag but it'd help to have an ordering mechanism for it, too.