65291 - [RFE] Ability to do multiple searches without clobbering the first search

Status: VERIFIED DUPLICATE of bug 24896

(Bugzilla :: Bugzilla-General, enhancement)

Description

[Keyser Sose]

Please please please, for the sake of the sanity of the bug triagers code
Bugzilla so it doesnt clobber the results from the first search you do.  For
example:

1) Run any bugzilla query
2) On the list that comes up click on any bug to get its details
3) Open a New Window
4) Run another bugzilla query
5) Go back to first window and click on any of the links such as: Next, Prev,
First, Last
6) Watch as bugzilla goes to the first result of the other query.


This may not seem like a big deal but when your looking for duplicates of an
unconfirmed bug, everytime you want to go to the next bug you have resubmit the
query, thus losing your place. Its a waste of time, and drives the bug triagers
insane. Please please fix :)

Comment 1

[Dave Miller [:justdave]]

This was discussed in IRC this evening.  Possible solution:

Assign each query a number.  Create a new cookie with each query, with that 
number in the cookie name.  Each time a user does a query, use whatever the next 
unused number is.  That number can then be placed in the "Prev", "Next", "Show 
List", etc. links so it knows which one to use when the link is clicked in that 
particular window.

Pick a reasonable number of queries (10?) and start deleting cookies when you get 
more than that many of them, to prevent cookie bloat.

Comment 2

[Keyser Sose]

*** Bug 65289 has been marked as a duplicate of this bug. ***

Comment 3

[Jesse Ruderman]

Can this be done without destroying the "visited" state of buglinks on query 
result pages?

Comment 4

[Dave Miller [:justdave]]

Ooohhh...  yeah, you'd need to have some way in the bug link to tell the newly-
viewed bug which buglist it was linked to from.  Hadn't thought about that.  
Ouch.

Comment 5

[Dave Miller [:justdave]]

Hmm, thought on that subject....
The cookies actually store a list of bug numbers (in the current implementation 
already in use).  If it continues to do that, all it would need to do is look to 
see which cookie it's mentioned in, then use that one.  If it was a hit in more 
than one query, perhaps supply more than one set of Next/Prev/First/Last/Show 
links, with the query numbers in front of each line...

Comment 6

[Jacob Steenhagen]

This has been brought up before, but the fundemental problem still remains... 
the cookie is the easiest way to deal with the buglist but at the same time 
it's a browser specific thing, not a window specific thing.

*** This bug has been marked as a duplicate of 24896 ***

Comment 7

[Matthew Tuck [:CodeMachine]]

V.

Comment 8

[Dave Miller [:justdave]]

moving all closed Bugzilla bugs to the new Bugzilla product.
This batch is DUPLICATE/INVALID/WORKSFORME/WONTFIX
reassigning to default owner and QA in case of the bug being reopened.
Clearing milestones, since we really shouldn't have them on these types of
resolutions.  Sorry for the spam everyone...

Comment 9

[Markus Gerstel]

Verification got lost