1

So, I've found that by editing the workflow I can tell FogBugz in MOST cases to STOP TRYING TO HELP ME, and leave the assigned-to field alone when I set a status... but not in all cases.

But not all status "types" allow setting the (No Change) option. Specifically re-opening a closed case. Is there a way to get FogBugz to just get the heck out of the way?

This is the most painful bug tracking software I've ever used, due to so many things like this. Please help if you can.

flag

2 Answers

1

As you pointed out, you can edit your workflow and specify (No Change) to prevent FogBugz from auto-assigning cases on status change.

The reason you can't select (No Change) upon re-opening a case is because when a case is closed, it is unassigned (or, more accurately, assigned to a special "CLOSED" user).

You can specify what happens when a case is re-opened, though. If you set it to be assigned to the Case Closer, it'll effectively work as though FogBugz never changed the assigned to.

There's tons of flexibility in the Workflow plugin, and once you've got it setup the way you want, you don't have to think about it.

link|flag
Rob, thanks for your answer. I hadn't realized FB is changing the assigned-to on closed items. IMHO, that is completely borked. Now I'll have to ask "is there a way to turn THAT off?" IMHO, that is completely unacceptable behavior. I suppose its clear that Joel used to work for Microsoft.. Maybe he is the one behind the paperclip after all :) – Travis Laborde Apr 27 2010 at 15:13
0

The question is why would you want to assign a case to someone when that case has already been closed? It is, by definition, complete and should not be assigned to anyone. Assigning a closed case to someone would be the equivalent of "This has already been done please do it". I think you are simply misguided in the difference between "Assigned To" and "Closed By". Further, if you simply would like to reassign the case upon reopening to the person that closed the case, that functionality is already there, I believe.

If you are looking for way to see who closed the case, enable the "Closed By" column in your filter.

If you would like to search FogBugz in reference to who closed a case use the search: closedby:"name here"

link|flag
I find the concept of "un-assigning" an item when it is closed to be completely un-intuitive and counter-productive. Show me all of Travis' cases that have been closed in the past month. Travis didn't open the case. Travis didn't close the case. But Travis was responsible for the work. IMHO, that is what "assigned-to" means. Especially given that FB says that if Travis works a case, he can only resolve it, not close it. So he wasn't the closer anyway. What is misguided is Fogbugz forcing this pattern. And that since Kiln is so cool, I'm "forced" to use it. – Travis Laborde May 11 2010 at 11:09
One search axis that might help you is the "alsoeditedby"...it still doesn't sound like quite what you're looking for, but it will give you a list of any case you've edited at any point. E.g. lastedited:"this month" alsoeditedby:me – db♦ May 11 2010 at 14:18
You just have to reinforce the FogBugz system with some human behavior. For example, if Travis works the case, then he must be the one to resolve it. Then you can easily search / filter with: resolvedby:"Travis" status:"closed" closed:"last month...today" type:"cases" I'll definitely agree that FogBugz "forces" quite a few patterns, but usually you can just think it through from another angle and do whatever it is you wanted to do, anyway. All systems have their own way of doing various little things. – Sergei May 12 2010 at 8:27

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.