Closed Bug 1283934 Opened 8 years ago Closed 6 years ago

New Fields: last-good/last-good-disabled/first-bad in bugs that have -[product]-statusNN flags

Categories

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

Product:
bugzilla.mozilla.org
Component:
General
Version:
Production
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: emceeaich, Unassigned)

References

Details

User Story

As a bugzilla user, I want to see at a glance the regression range of a bug, so I can make decisions about the bug.
The status-firefoxNN flags require substantial client processing to determine regression and fix ranges for bugs. 

We'd like a set of computed fields, based on the -status-firefoxNN flags to make a bug's regression range more immediately obvious and/or signal an inconsistency in a bug's metadata.

last-good: non-decimal version number of earliest firefox release where -status-firefoxNN is unaffected
last-good-disabled: non-decimal version number of earliest firefox release where -status-firefoxNN is one of fixed, disabled, verified-disabled, or verified
first-bad: non-decimal version number of earliest firefox release where -status-firefoxNN is affected

These fields should be displayed in a bug's summary.

It would be good if there's a field shadowing this that indicates which train–nightly, aurora, beta, release, previous-release–corresponds to the version numbers above.
This is higher priority than the "which release train" work.
Priority: -- → P1
{Unblock}bug fix(In reply to Emma Humphries ☕️  [:emceeaich] (UTC-8) NEEDINFO? me from comment #0)
> The status-firefoxNN flags require substantial client processing to
> determine regression and fix ranges for bugs. 
> 
> We'd like a set of computed fields, based on the -status-firefoxNN flags to
> make a bug's regression range more immediately obvious and/or signal an
> inconsistency in a bug's metadata.
> 
> last-good: non-decimal version number of earliest firefox release where
> -status-firefoxNN is unaffected
> last-good-disabled: non-decimal version number of earliest firefox release
> where -status-firefoxNN is one of fixed, disabled, verified-disabled, or
> verified
> first-bad: non-decimal version number of earliest firefox release where
> -status-firefoxNN is affected
> 
> These fields should be displayed in a bug's summary.
> 
> It would be good if there's a field shadowing this that indicates which
> train–nightly, aurora, beta, release, previous-release–corresponds to the
> version numbers above.
Flags: needinfo?(commrer)
~~~~{bugfix}
Flags: needinfo?(commrer)
Assignee: nobody → dkl
Status: NEW → ASSIGNED
Assignee: dkl → nobody
Status: ASSIGNED → NEW
Priority: P1 → P2
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.