A forum for technical support discussion related to Fogbugz.
How does one tell a developer specifically which issues to work, in order? For instance we have 5 bugs today that are marked as IMMEDIATE, but one of them needs to be done first. How do various people solve that with FB? My boss would really like a way to order the bug list with in the priority groupings. I know we could just go into MSSQL and add more priorities so it can be more granular ... is that what others have done? Just looking for ideas.
Thursday, December 6, 2007
One way you can prioritize within priority is to use due dates (make one "Immediate" case due today, and the others due tomorrow, or you could even get more fine-grained by using different due times within a day).
Another possible workaround would be to reserve the top priority for a single case at a time, but that means squinching down all other cases into 6 priorities instead of 7.
We often have this need also.
What we do is to edit the case titles:
(first) Fix the FOO function
(second) Test against jitterbug framework
It works, if inelegant.
Thursday, December 6, 2007
I tried using one of the User Defined fields as a "Sequence" number [which we had in our In House Bug Tracker Thingie]. However, items that have NO value in the User Defined sort first. (I haven't tried a reverse-sort, it might be that high numbers would sort first, and blanks last, in a reverse sort)
I think it would be good if "priority" was both the 1-7 thingie, and also a sequence number which could be influenced by drag-and-drop in the case list, or some sort of promote/demote icons. New items could be allocated the next-highest-sequence number, so would sort in date-created order, initially.
We're experimenting with solutions to this problem as well. Here's what we've done:
The default priority for new cases is moved from 3 to 5.
Priority values 2-4 are assigned at regular semi-weekly meetings. Cases may also be moved into these priority values whenever needed.
Priority 1 now has a title of "Stop what you're doing and do this right now."
Priority level 6 is "back burner"
Priority level 7 is "things we don't want to forget about"
We've found that the last component of making sure people are working on things in the right order is simple verbal communication, usually from the big boss on down the tree as to what needs to be fixed first.
If developers finish all the priority 2 tasks then they move on to priority 3 and then priority 4. There's always more than enough in those three levels to keep everyone busy until the next monday or wednesday meeting to see what needs to move up the list from priority 5 or deeper.
Monday, December 10, 2007
This topic is archived. No further replies will be accepted.Other recent topics