Question

This is probably only a concern because our FB instance runs pretty slowly, particularly for complicated searches/filters, but anyway...

Is it possible to change the behaviour for closing a case to not revert to the current search/filter but simply to remain showing the current (now closed) case instead? This is particularly painful if I pull up a large/slow filter and then open up a bunch of cases in tabs and want to review and close them - each time I hit close for one bug this causes a re-request for the full filter contents in that tab.

NB Since we upgraded to FB 7.x and rebuilt our MySQL DB response times are much improved, so less of a pain. However I'd still prefer not to lose context when I close a bug; as one example I'll often close a bug as duplicate and then want to navigate to the master bug for the issue - at the moment I need to remember to click through to the related bug first before closing...

Case FC900688

Answer 1

As of FogBugz 8.2 there is now an option to change the "Close Case Action" to either redirect you to your current filter (the way it always has), or remain on the current case's details page.

This setting can be found under My Settings -> Options -> Close Case Action:

Answer 2

There are significant performance improvements in 7 so I would definitely upgrade and see how that affects this issue. That said, I do encounter something like this for the occasional slow search. Here's the method I use to prevent the slow-down:

As you said, I'm usually opening a number of cases from a slow search in tabs and then working with them. Once they're all in tabs, I don't need the search anymore, so I just click List Cases to replace the search with my current (much faster) filter. Now when I close one of the cases, I'm shown my current filter which doesn't slow me down like the search would.