Sort important products to top of list on query page




17 years ago
11 years ago


(Reporter: gerv, Unassigned)




(1 attachment, 1 obsolete attachment)

(b.m.o.-specific customisation)

We need to customise our template to sort the important products to the top of
the products list on the query page, and then pre-select Browser and MailNews.
This is what most people want, and it'll speed up searches.

Created attachment 102374 [details] [diff] [review]
Patch v.1

This should work for b.m.o.

gerv: PSM is alo very important. Near all SSL bugs are going to Security:general
at the moment.
Comment on attachment 102374 [details] [diff] [review]
Patch v.1

>+              [% key_products_regexp = key_products.join("|") %]
>               [% FOREACH p = product %]
>+                [% NEXT IF %]

This doesn't work, even for bmo's limtied product list - "Browser
localisations" matches (Browser|MailNews), so that product won't get displayed
Attachment #102374 - Flags: review-
Thanks for making me think about this harder :-)

Bugs created between 2002-10-01 and 2002-10-08 now in the following components:
PSM:                     12
Chimera:                 90
Phoenix:                139
Mozilla Localizations:    2
Tech Evangelism:         36

I will remove "Mozilla Localisations" from the list of important products; but I
don't think PSM can make a case for being added.

Created attachment 104274 [details] [diff] [review]
Patch v.2

Try this - the more conventional (and sensible) approach.

Attachment #102374 - Attachment is obsolete: true
Comment on attachment 104274 [details] [diff] [review]
Patch v.2

The JavaScript code for updating the component, version, and milestone lists
assumes products are listed alphabetically (or at least according to some order
it knows).  After applying this patch, clicking "MailNews" causes Bugzilla's
components to appear, because Bugzilla was second in the list before this patch
made MailNews the second product.
Attachment #104274 - Flags: review-
Drat. :-) I'll investigate this tonight, but this may require too much
JavaScript surgery to do in time, which would suck. If anyone else wants to take
a shot at this, feel free.

I ran out of time last night and this morning as well. Help! :-)

No longer blocks: 176570
When we rewrite the JS to fix bug 173583, then we'll be able to do this.

Depends on: 173583
Priority: -- → P3
Target Milestone: --- → Bugzilla 2.18

Comment 10

15 years ago
Unloved bugs targetted for 2.18 but untouched since 9-15-2003 are being
retargeted to 2.20
If you plan to act on one immediately, go ahead and pull it back to 2.18.
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Severity: normal → enhancement
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004.  Anything flagged
enhancement that hasn't already landed is being pushed out.  If this bug is
otherwise ready to land, we'll handle it on a case-by-case basis, please set the
blocking2.20 flag to '?' if you think it qualifies.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22


13 years ago
Assignee: gerv → query-and-buglist
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Bugzilla 2.22 → ---
Life has moved on past this bug.

Last Resolved: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.