Closed
Bug 569758
Opened 16 years ago
Closed 16 years ago
Need 1.9.2.6 values for 1.9.2-branch custom fields
Categories
(bugzilla.mozilla.org :: Administration, task)
bugzilla.mozilla.org
Administration
Tracking
()
RESOLVED
FIXED
People
(Reporter: dveditz, Assigned: marcia)
Details
Fennec 1.1 is branching and taking the "1.9.2.5" release so we need to add 1.9.2.6 in order to continue with our next security release plan. Please add
".6+" as a value in the "blocking1.9.2" custom field
".6-fixed" as a value in the "status1.9.2" custom field
no renaming or changing the value of existing bugs, we need these as additional values.
| Reporter | ||
Comment 1•16 years ago
|
||
justdave: with Marcia away is this something you could do for us?
[are these values hardcoded or require raw SQL to administer, or is there a panel that could be made available to people--like myself--who are able to administer flags? If not is there an RFE on file?]
| Assignee | ||
Comment 2•16 years ago
|
||
Resolving fixed as these have been added. Only newly created custom flags require backend work, which is customarily done by Reed. If you can administer flags you should be able to add these values.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Comment 3•16 years ago
|
||
Editing custom flag values requires the "admin" bit - editcomponents (which allows you to edit normal flags) isn't sufficient. The list of active admins isn't very long (reed/marcia/justdave?), so if any of them are away/busy with other things/not monitoring these incoming bugs, requests like these linger.
| Assignee | ||
Comment 4•16 years ago
|
||
There are actually many more admins than just the three of us - I count 19 - many of them are IT. So it really comes down to assigning someone to be the backup when Reed and I are not available.
Comment 5•16 years ago
|
||
I deliberately only included active admins in my list :)
Updated•15 years ago
|
Component: Bugzilla: Keywords & Components → Administration
Product: mozilla.org → bugzilla.mozilla.org
You need to log in
before you can comment on or make changes to this bug.
Description
•