Closed
Bug 138351
Opened 22 years ago
Closed 14 years ago
add option to not clear existing buglist
Categories
(Bugzilla :: Query/Bug List, enhancement, P3)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: jayvdb, Unassigned)
References
Details
Attachments
(1 file)
1.84 KB,
patch
|
Details | Diff | Splinter Review |
Currently when using multiple buglists, there is no way to avoid a 'primary' buglist from being replaced with new queries. Whilst bug 24896 is addressing the problem of multiple fully functional buglists, a simple workaround would be to allow the user to choose that a query's results does not overwrite the existing buglist. (see bug 24896 comment 9)
Reporter | ||
Comment 1•22 years ago
|
||
We have this implemented as another cmdtype 'doitonce' * Run this query and save buglist * Run this query once Suggestions welcome.
Reporter | ||
Comment 2•22 years ago
|
||
Comment 3•22 years ago
|
||
IMO "and retain bug list" should be a checkbox to the right of "Run this query", defaulting to checked. Should we do this as a short-term measure? People have been asking for this sort of thing for a while. Gerv
Reporter | ||
Comment 4•22 years ago
|
||
As I see it, there are three scopes to which this option may be provided: 1) Custom queries created on query.cgi, (this is all attachment 'v1' provides) 2) Custom & Stored queries run from query.cgi, (from what I can see the bug list order is provided in this way) 3) or the option persists with a stored query, allowing a stored query in the footer to be run without clearing the bug list. I can see the need for stored queries to be able to use this option (2), however (3) might be overkill as I can not find another query option which operates in this way, however bug 135449 has been raised to change the sort order from (2) to (3). It is important to establish the scope, as each of these may require that the option be presented in a slightly different manner, in order to be intuitive.
Comment 5•22 years ago
|
||
I don't see a major problem with removing this option later so it may as well be done as an interim measure.
Severity: major → normal
Priority: -- → P3
Target Milestone: --- → Bugzilla 2.18
Comment 6•22 years ago
|
||
I found a workaround: Use different browsers, e.g. Netscape 4 for going through all bugs of your main query, and Mozilla for doing the temporary queries. This way, the intermediate searches don't affect your cookie in the main browser.
Comment 7•22 years ago
|
||
*** Bug 188743 has been marked as a duplicate of this bug. ***
Comment 8•20 years ago
|
||
This would be handy, but the patch is bitrotten and nobody seems to be working on it.
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Updated•20 years ago
|
Severity: normal → enhancement
Comment 9•19 years ago
|
||
This bug has not been touched by its owner in over six months, even though it is targeted to 2.20, for which the freeze is 10 days away. Unsetting the target milestone, on the assumption that nobody is actually working on it or has any plans to soon. If you are the owner, and you plan to work on the bug, please give it a real target milestone. If you are the owner, and you do *not* plan to work on it, please reassign it to nobody@bugzilla.org or a .bugs component owner. If you are *anybody*, and you get this comment, and *you* plan to work on the bug, please reassign it to yourself if you have the ability.
Target Milestone: Bugzilla 2.20 → ---
Updated•18 years ago
|
QA Contact: mattyt-bugzilla → default-qa
Updated•15 years ago
|
Assignee: jayvdb → query-and-buglist
Comment 10•14 years ago
|
||
Instead of adding an option, we're just going to fix bug 24896.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•