Closed
Bug 1275005
Opened 9 years ago
Closed 9 years ago
Create a prototype for the bug triage dashboard based on re:dash
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mdoglio, Assigned: mdoglio)
References
Details
Attachments
(1 file)
75.39 KB,
text/csv
|
Details |
Let's start to explore/validate the available data using a prototype based on re:dash
Assignee | ||
Comment 1•9 years ago
|
||
Here [1] is the code I used to extract the bug data from the bugzilla rest api; the code assigns a release cycle and channel to each bug, based on the release calendar found at [2]
[1] https://gist.github.com/maurodoglio/68673e5b9c04c7212b69414db87e5e67
[2] https://wiki.mozilla.org/RapidRelease/Calendar
Assignee | ||
Comment 2•9 years ago
|
||
I setup up a new redash instance and I loaded the data exported with the script above.
The instance is available at http://ec2-54-201-73-200.us-west-2.compute.amazonaws.com.
I configured the re:dash authentication to work with the mozilla email accounts via Google+.
Assignee | ||
Comment 3•9 years ago
|
||
Here is the content of the regression_bugs table in csv format.
Updated•9 years ago
|
Points: --- → 3
Priority: -- → P1
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → mdoglio
Assignee | ||
Comment 4•9 years ago
|
||
The data etl script now lives here [1].
A visualization of the regression bugs grouped by release cycle and release channel is here [2]
[1] https://github.com/maurodoglio/bz2db/blob/master/update_bugs.py
[2] https://sql.telemetry.mozilla.org/queries/567#955
Assignee | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•