Collect problem statement(s) for the bug triage dashboard

RESOLVED FIXED

Status

Cloud Services
Metrics: Pipeline
P1
normal
RESOLVED FIXED
2 years ago
a year ago

People

(Reporter: mdoglio, Assigned: mdoglio)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

2 years ago
This should drive the implementation of the data collection and data visualization parts of the dashboard.
(Assignee)

Comment 1

2 years ago
Copy&pasting here some notes from a discussion with Emma a few wekks ago:
 
* Ratio of regressions + bugs in new features found pre-beta/beta/release.
  * "Over the FFx XX release cycle, we found 50 regressions, 40 of which were in Nightly, 5 in Aurora, 4 in Beta, and 1 in Release"
  * Focus on Regressions
  * Which point on the train the bug appeared (use version, release flags and filing date) 
* Regression definition (see notes)
  * We will need to 'debug' the data to validate what we are getting
  * Nightly regressions are noisy and may need to be left out
  * Limit to regressions identified by Softvision and Internal/Trusted Contributors
* May not do new feature bugs in first iteration
  * If a feature has a test plan, then there may be a simple way to catch those, QA can flag those with whiteboard, or a keyword
  * trickier part is post release feature filings

Updated

2 years ago
Points: --- → 3
Priority: -- → P1

Updated

2 years ago
Assignee: nobody → mdoglio
(Assignee)

Updated

a year ago
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.