Closed Bug 584632 Opened 14 years ago Closed 13 years ago

"Plugins" product lost Gecko release tracking flags (multi-state fields)

Categories

(bugzilla.mozilla.org :: General, defect)

defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 628383

People

(Reporter: alqahira, Unassigned)

Details

(Keywords: regression)

When timeless moved all the plug-in bugs into their own product, I yelled at him because it meant that we were no longer able to track release blocking issues, etc., particularly since one of the components in that product is actually shipped as part of Gecko (JEP).  So timeless got the flags appearing there.

Today I went to comment in bug 584408 about what release(s) bug 551327 landed in time for, and I discovered that the flags were gone (and I had to instead infer from the approval flags on the "patch", which worked OK for this purpose, but is not helpful for tracking blockers, performing QA, etc.--looks like QA never did any post-landing verification on that bug due to missing flags).

SWAG is that the Bugzilla upgrade broke this, but I really can't say for sure.
Assignee: marcia → nobody
Component: Bugzilla: Keywords & Components → Bugzilla: Other b.m.o Issues
QA Contact: timeless → other-bmo-issues
i have no visibility to those flags unfortunately, they aren't flags, they're custom fields. it'd be nice if i did...
OS: Mac OS X → Windows 7
OS: Windows 7 → All
Hardware: PowerPC → All
Hrm, my memory is bad, then; I know I complained about something like flags, and you added *something*, but…at any rate, it's still a regression from when we were able to block releases on plug-in and JEP bugs ;)

Anyway, Josh just asked about this in bug 571537, so it is a problem, and we keep inventing kludges like we've been doing for TE bugs to work around the problem :(
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
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.