A forum for technical support discussion related to Fogbugz.
We're new to Fogbugz. It was my understanding that only the creator of a case could close that case. However, the developer (the person a case has been assigned to) seems to be able to not only resolve the case but also close it.
Is there a setting somewhere that I am missing? I definitely do not want this behavior!
Thanks in advance.
Friday, December 9, 2005
This is by design. A case is assigned to the opener when it is resolved for them to close but FogBugz doesn't force them to be the only person who can close the case.
This would restrict the way users interact with FogBugz. Sometimes you do need to close a case, even though you weren't the opener.
Ouch. That can make it easy for something to slip between the cracks -- if a developer closes the case himself, the "fix" may never be properly reviewed.
Personally, I would have liked this to be an option I can set, either globally or by developer.
Thanks for the response, though. I will give some thought to this and see whether we can live with it or if we're going to use the 30-day money back guarantee.
Friday, December 9, 2005
90 day guarantee!
You have 3 months to decide :)
If you have a developer who you've told that cases have to be reviewed by someone else and they continue to close cases, this may be something FogBugz can't solve.
You can however get a list of all cases that were closed today (or this week) and take a look at them to see if that is happening.
Forcing only the owner to close a case in practice can become tedious and a hinderance which is why FogBugz works with whatever process you put it into.
Can I point to http://support.fogcreek.com/default.asp?fogbugz.4.7647.0 here? :-)
Saturday, December 10, 2005
We should also point out that as long as you have email notifications turned on, the opener of a case will always be notified when the case is resolved. So the opener is kept in the loop.
In practice, this makes it nearly impossible for something to slip between the cracks. And it removes the need to force only the opener to close a case, since as Michael pointed out, this can become a hindrance.
Thanks for the feedback and suggestions. We'll see how it works out.
At the moment we're only using Fogbugz for one product while we test it. Hopefully this won't be an issue.
I understand about the need for flexibility -- I just wish I could have the option of enforcing the closing policy.
Overall impression of Fogbugz so far is that it is excellent.
Sunday, December 11, 2005
This topic is archived. No further replies will be accepted.Other recent topics