Open
Bug 250969
Opened 20 years ago
Updated 18 years ago
Parameters need to have per product or classification override
Categories
(Bugzilla :: Whining, enhancement)
Tracking
()
NEW
People
(Reporter: jk, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113
The whine params and possibly others, need to be set on per product basis.
I have products that receive many bugs and are not so urgent, but there are
products that have a higher urgency and I need them to whine way faster than
the rest. I'd like to be able to set some products to whine after 2 days while
others can take a week or more.
Reproducible: Always
Steps to Reproduce:
No steps, its enhancement request.
Reporter | ||
Updated•20 years ago
|
Version: unspecified → 2.16.5
Comment 1•20 years ago
|
||
Bug 185090 should take care of this since all whining becomes query-based
Are there any such cases not covered?
Depends on: 185090
Reporter | ||
Comment 2•20 years ago
|
||
That bug might fix whining, but what about other global parameters?
And what about severity categories? What about displaying platform
and os, you might have products that don't have these at all.
Similar with commenton* params, which should be very much product
dependent and not global.
Updated•20 years ago
|
Assignee: justdave → erik
Component: Email Notifications → Whining
Comment 3•20 years ago
|
||
Erik, what do you think about this one? (It's been pending for 6 months now.)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 4•19 years ago
|
||
(In reply to comment #3)
> Erik, what do you think about this one? (It's been pending for 6 months now.)
Make that a year. Sorry
Well, the original stated issue on this one will be solved when whineatnews can
be phased out (it cannot yet).
As for having per-product override for *every* parameter, I'm against it.
Editparams is complicated enough as it is, and I have little faith that it will
be fixed any time soon. Maybe it'll make more sense if bug 46296 ever lands,
but until then we're talking about complicating the interface in a way that will
not make it through the review process.
OK, having said all that, it almost makes sense to want some of these parameters
to work differently, say, using classifications, and with the slick interface
envisioned by bug 46296, it could be something to think about.
Until then, I can't think of an easy way to accomplish this. The closest I can
get is to suggest a whole different installation for a product that needs a
different configuration. That's kind of yucky.
In the meantime, the new whining system might help alleviate any aches and pains
caused by a need for this feature.
I'll leave this open as a long-view kind of enhancement.
Depends on: 46296
Summary: Whine (and other params) need to have per product override → Parameters need to have per product or classification override
Updated•18 years ago
|
QA Contact: mattyt-bugzilla → default-qa
Updated•18 years ago
|
Assignee: erik → whining
You need to log in
before you can comment on or make changes to this bug.
Description
•