2

My "todo" bookmark folder in Chrome contains two webpages:

When I middle-click the folder, both pages are opened simultaneously in tabs.

However, instead of loading each filter in its respective tab, the same filter is loaded in both tabs. Sometimes, both tabs show filter 19, and other times, both show filter 49 (and sometimes it even works as expected).

flag
Vote up a request to change this design: fogbugz.stackexchange.com/questions/10130/… – Michel de Ruiter Mar 19 at 10:08

2 Answers

2

The "right" way to bookmark two filters is to grab the permalink url from under the more menu on the right side of the page.

This has the downside that it's a serialized version of the filter, so if you make changes to a saved filter they won't be reflected, but I think it works more reliably loading two at the same time.

Another trick is to construct your filters as searches, which don't count as filters. You can execute as many searches as you like without changing the current filter.

Note that there's other fallout from any workaround, such as the next and previous arrows will behave unpredictably.

link|flag
3

That's how FogBugz filters work. Only one can be active at a given time. Which behaviour you see depends on which filter request reaches the server last, and the order in which the server responds to the requests to display the filters.

If you really want to see both filters, open one and wait for FogBugz to start sending its response before opening the other filter in a new tab. Note that whichever filter you view last will also be set as your "current" filter, meaning that is the filter you will see when you click on the "List Cases" link at the top of the page.

link|flag
Thank you for explaining the behavior I'm observing. As I understand it, the work-around is stop using tabs the way I'm used to. Is there a fix planned, or is this officially by-design? – Emmett Feb 15 2011 at 20:40
It was officially designed before tabbed browsing was all the rage :). The concept of "current filter" is rather deeply ingrained in FogBugz, so the planned fix has a lot of inertia to overcome. – Ted Feb 15 2011 at 21:19

Your Answer

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