Closed
Bug 533431
Opened 15 years ago
Closed 14 years ago
blocking-thunderbird3.0 and status-thunderbird3.0 multi-state flags not cleared when moving to different components.
Categories
(bugzilla.mozilla.org :: General, defect)
bugzilla.mozilla.org
General
Tracking
()
RESOLVED
DUPLICATE
of bug 576609
People
(Reporter: standard8, Assigned: justdave)
Details
If someone moves a bug to a different component, then the multi-state flag isn't cleared if the flag doesn't exist in that component. This has happened in bug 519962 where the bug was flagged as blocking-thunderbird3.0 = ? but then moved to Core, where we don't have the blocking-thunderbird3.0 flags. I expect I can fix it by moving it back to a component where the state is valid and then back again, but it would be useful if at least the ? states for both blocking-thunderbird3.0 and status-thunderbird3.0 were cleared if necessary when moving.
Assignee | ||
Comment 1•15 years ago
|
||
This will be pretty difficult to implement... the fields are actually global, and not product-specific. We're using a little bit of smoke and mirrors in the templates to make them look like they're product-specific to avoid clutter on other products. This will probably be possible in Bugzilla 3.8, don't know if it's worth hacking for our site before then.
Reporter | ||
Comment 2•15 years ago
|
||
Ok, I don't think this is going to happen too often, so we can survive (I'll put a note somewhere pointing to this bug). I'm quite happy if we future this.
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Updated•13 years ago
|
Component: Bugzilla: Other b.m.o Issues → General
Product: mozilla.org → bugzilla.mozilla.org
You need to log in
before you can comment on or make changes to this bug.
Description
•