722054 - Need new custom fields for ESR10 releases

Status: RESOLVED FIXED

(bugzilla.mozilla.org :: Administration, task)

Description

[Daniel Veditz [:dveditz]]

We need custom flags for ESR project management. Similar to the other Firefox flags we need a tracking and status flag, but since it's a multi-release branch we'll need values more like the 1.9.2 fields.

Field:  tracking-ESR10
Values: --- (default)
        ?
        -
        .1+


Field:  status-ESR10
Values: --- (default)
        unaffected
        affected
        .1-fixed
        .1-verified
        wontfix

We'll eventually have more version values in there, but if we try to save work and pre-populate them now it becomes a big hassle should we have a future "chemspill" release. Those require either a user moving all the future-release bugs from one value to the next (generates bugspam and I think can't be done on many bugs at once) or a BMO admin renaming the values (our usual course of action). If there's only ever a "next release" value it's easy enough to rename it and create a new one with the old name, but if you had seven future values you'd have to rename each one in turn starting with the biggest and work your way back.

Placement
---------
These should show up on the same products as the status1.9.2 field -- it's more than just "firefox".

They can be placed in the expando "Tracking Flags" section right above the current 1.9.2 flags.

Comment 1

[:glob ✱]

done

Comment 2

[Mark Banner (:standard8)]

(In reply to Daniel Veditz from comment #0)
> We'll eventually have more version values in there, but if we try to save
> work and pre-populate them now it becomes a big hassle should we have a
> future "chemspill" release. Those require either a user moving all the
> future-release bugs from one value to the next (generates bugspam and I
> think can't be done on many bugs at once) or a BMO admin renaming the values
> (our usual course of action). If there's only ever a "next release" value
> it's easy enough to rename it and create a new one with the old name, but if
> you had seven future values you'd have to rename each one in turn starting
> with the biggest and work your way back.

If Bryon hasn't already, these could be added to the general list of versions & flags that get added at each release.

Comment 3

[:glob ✱]

(In reply to Mark Banner (:standard8) from comment #2)
> If Bryon hasn't already, these could be added to the general list of
> versions & flags that get added at each release.

wiki updated.