11

1

Using the workflow plugin I modified our workflow so that when resolving cases as fixed they are assigned to a virtual "QA Team" user. The QA team then select cases from this list when they move to work on the project.

This works nicely, except that it seems that Fogbugz automatically shows the "Resolve & Close" button when assigning to a virtual user. This results in developers closing cases by mistake when they meant to resolve them.

Would it be possible to make this optional? Either in the workflow plugin or directly in Fogbugz?

Fog Creek Case FC1838016

flag
It's a valid use case. – Rich Armstrong Sep 16 2009 at 21:21
This would be a big help. +1 – cdeszaq Mar 9 2010 at 13:59
I totally concur. My workaround in the meantime has been to make that a real user with a bogus password. This gets rid of the resolve and close button, but my QA team can still pull cases from a single place. – David Mitchell May 23 2010 at 3:22
It would also be useful to be able to specify which resolution status can also be immediately closed. In our work-flow, we'd like to hide the "Resolve & Close" button for Fixed/Implemented/Completed resolutions but allow it for others (Won't Fix, etc.) – nonplus May 28 2010 at 16:20
We need to be careful with this one, as this is the only way to allow people to see "Resolve & Close" without having to change the "Assigned To" value to themselves. – Rob Sobers Oct 11 2010 at 13:08

4 Answers

1

Case filed. We'll see if we can get this into an future release.

link|flag
Excellent. Looking forward to it. – Roman Jan 17 2010 at 12:00
1

I'm not sure how this would be implemented, but I'm pretty sure it should be possible.

link|flag
1

If you install the BugMonkey plugin, you can add the following CSS to hide the "Resolve & Close" button:

#Button_ResolveAndClose {
    display: none;
}
link|flag
It appears that with the latest version, the editor is in an IFrame and is not impacted by the CSS change. NOT HAPPY! – Doug Napoleone Sep 7 at 21:24
@Doug I'm not sure I understand your comment. While the rich text editor lives in an IFrame, the buttons do not. This customization works just fine with the latest version of FogBugz. Do you have any other customizations applied that might be forcing the Resolve & Close button to remain visible? – db Oct 1 at 12:57
The above code doesn't work in 8.8. You need this javascript. js: $('a.resolve').remove(); – Todd Day Mar 8 at 6:10
0

I am using the BugMonkey hack right now which only partially works to remove the "Close" options in any of the interfaces so adding this feature would be very helpful.

link|flag
To also hide Send & Close, use #Button_ResolveAndClose, #Button_SendAndCloseEmail { display: none; }. Any there any Close buttons left? – Michel de Ruiter Jan 9 2012 at 9:55
When you are viewing a "resolved" case, there is a "Close" link at the top and bottom of the case. I can get rid of the link itself but not the check box icon in front of it, which also does a "close". It makes it less obvious that there is a close option at that point but clicking the icon lets you close it. There is also a "Close" button in the "List Cases" view. – unknown (google) Jan 9 2012 at 20:07

Your Answer

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