Closed
Bug 1426168
Opened 7 years ago
Closed 7 years ago
Create a dashboard to track issue diagnosis burndown
Categories
(Web Compatibility :: Tooling & Investigations, enhancement)
Web Compatibility
Tooling & Investigations
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: miketaylr, Unassigned)
Details
Something like a weekly number of open "needsdiagnosis" issues, vs issues that were resolved, or moved to another stage. It might be difficult, since some issues skip diagnosis phase and go directly into contact...
But if we used a label to track the diagnosis work done for our Q1 OKR, it would be possible to track.
Bonus points if we include a graph for Bugzilla Tech Evangelisms issues as well.
Reporter | ||
Comment 1•7 years ago
|
||
(Note: this isn't an issue on webcompat.com repo because I'm going to deploy this dashboard on my own personal site or on a random github repo page)
![]() |
||
Comment 2•7 years ago
|
||
https://github.com/webcompat/web-bugs/milestone/3
A very simple thing to do would be as a first step, every day at the same time have a cron job requesting and extracting the number of issues for this milestone (needsdiagnosis).
Something like start of the day at the IDL (in the Pacific the line for changing date). UTC+12
Location Local Time Time Zone
UTC+12 Wednesday, 3 January 2018, 00:00:00 UTC+12
Tokyo Tuesday, 2 January 2018, 21:00:00 JST UTC+9
San Francisco Tuesday, 2 January 2018, 04:00:00 PST UTC-8
so we will be able to access the first raw number.
The secondary numbers to track. It's
- How many new needsdiagnosis during 24h.
- How many less needsdiagnosis during 24h.
Reporter | ||
Comment 3•7 years ago
|
||
We're building this over on GitHub now: https://github.com/webcompat/webcompat-metrics/projects/2#card-7852227
(awkwardly closing as INVALID, because I can't dupe it...)
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•