Open
Bug 376151
Opened 17 years ago
Updated 2 months ago
After search, "File a bug" link should prefill fields from the search terms
Categories
(Bugzilla :: Query/Bug List, enhancement)
Tracking
()
NEW
People
(Reporter: timeless, Unassigned)
References
()
Details
Attachments
(1 obsolete file)
Steps: 1. write a complicated query that gets 0 or more than 0 results (these cases should be handled slightly differently) 2. click the File a new bug link at the bottom of search results Actual results (more than one result): 1' Sun Apr 1 2007 03:05:06 PDT This is an ancient Aztec death curse. All who see it will die horribly. Too bad if you looked! ID Sev Pri OS Assignee Status Resolution Summary 339684 min P5 All attach-and-request@bugzilla... NEW potentially settable flags really don't scale well past 5 items One bug found. CSV | Feed | iCalendar | Change Columns | Edit Search as File a new bug in the "Bugzilla" product 2' https://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla Expected results: All fields that have the same value in each query result should be prefilled. That means the severity should be prefill: * Component * Severity * Priority * OS * (Platform) * dependencies * target milestone * version Things to be included only if they're visible in search results: * keywords (note: if there are two bugs found and one has "one,two" and the other has "two,three", then "two" should be prefilled). * CC (see logic for keywords, a note should appear below the CC box listing the users who matched all bugs, and the users [user at a time] w/ a list of their cc's for those who don't match all bugs) Things to always exclude: 1. resolution :) 2. status 3. alias 4. reporter Things to be excluded by default: 1. Summary 2. Assignee/QA Contact Things to be included if they're part of the search criteria: 1. CCs (any explicitly listed or matching CC whitelist queries) 2. keywords (see CCs) 3. dependencies (...) Expected results (no results): * All fields that the user explicitly searched for a single value should be prefilled * this includes the summary field * this includes the alias field The reason I'm filing this bug is that I don't want to have to manually fill the component when I search for only bugs in one component. Note that this means that if I search for bugs in "component:General" and all bugs match only one product (Core) then I expect both product and component to be prefilled. I suspect that today nothing would be prefilled.
Comment 1•16 years ago
|
||
Rearranging this component to not have me as the default assignee, so that it doesn't appear like I'm intending to work on bugs that other people could be taking care of if they didn't think I was already doing them. If this bug is a software issue on b.m.o and you'd like to fix it, the modified source is now available for the patching (see bug 373688). Reassigning to the new default owner.
Assignee: justdave → nobody
QA Contact: reed → other-bmo-issues
Updated•14 years ago
|
Assignee: nobody → query-and-buglist
Component: Bugzilla: Other b.m.o Issues → Query/Bug List
Product: mozilla.org → Bugzilla
QA Contact: other-bmo-issues → default-qa
Summary: File a bug link should prefill all fields which have a single matching value or were specifically requested by the user → After search, "File a bug" link should prefill fields from the search terms
Version: other → unspecified
Comment hidden (spam) |
Updated•2 months ago
|
Attachment #9385304 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•