Create Visualization for mean time to resolve S1-S2 functional defects
Add a top-level chart under group views in https://quality-dashboard.gitlap.com/groups/gitlab-org
Create similar visualization the same as https://docs.google.com/spreadsheets/d/1p6V_jRZDbfTx0Vlq5lpp4oREWLRKkYpn13tyBHLEEaA/edit#gid=802418754
- Add 2 charts one for all bugs another for only customer bugs
- Add rolling average line
- Add total average, p85 and p95 percentiles
- Show closed items
Relates to
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Mek Stittri changed milestone to %12.1
changed milestone to %12.1
- Mek Stittri mentioned in issue gitlab-com/www-gitlab-com#4351 (closed)
mentioned in issue gitlab-com/www-gitlab-com#4351 (closed)
- Mek Stittri marked this issue as related to gitlab-com/www-gitlab-com#4351 (closed)
marked this issue as related to gitlab-com/www-gitlab-com#4351 (closed)
- Contributor
I guess we would need to combine the results of two searches to achieve this because we're searching for bugs with ~S1 or ~S2 labels.
Something like:
Example: Time to resolve S1 and S2 bugs (all)
- Find all closed issues labelled S1 and bug
- Find all closed issues labelled S2 and bug
- Combine searches
- For all issues
- Extract the difference between the
created_at
andclosed_at
attributes
- Extract the difference between the
- Group by
closed_at
month - Add for each group (month):
- mean time to close
- 85% percentile
- 95% percentile
- Mark Fletcher added Quality insights typefeature labels
added Quality insights typefeature labels
- Contributor
I thought we can probably add a new feature which allows us to query with OR? Maybe something like...
filter_labels: - bug filter_labels_one_of: - S1 - S2
?
Collapse replies - Author Contributor
This would be great once we have the project inclusion in. Right now we need to evaluate the same data population. Which currently resides in Insights.
- Mek Stittri added to epic &1362
added to epic &1362
- Author Contributor
@markglenfletcher @godfat can we please have an estimate on the effort here. I am planning to update in tmr's Dev Metrics meeting. A rough estimate is fine. We need to get started on this.
Collapse replies - Contributor
@meks
I am really not sure how to implement this yet, so I am not sure. I might expect roughly a week maybe?@markglenfletcher Do you know if we can render this easily, assuming we have backend data available already?
- Contributor
We already have combo bar line charts in the dashboard but we don't have any that utilise multiple datasets. It looks like we need to represent:
- Per month
- Bar
- Mean time to close
- 85%
- 95%
- Line
- 8 month Moving avg (mean time to close)
- 8 month Moving avg (85%)
- 8 month Moving avg (95%)
- Bar
- Per month
- Lin Jen-Shin changed weight to 7
changed weight to 7
- Mark Fletcher mentioned in merge request !105 (merged)
mentioned in merge request !105 (merged)
- Contributor
!105 (merged) won't close this yet but it does a lot of the groundwork
- Author Contributor
I am going to close this since we now have https://quality-dashboard.gitlap.com/groups/gitlab-org/time_to_close_bugs
- Mek Stittri closed
closed
- Mek Stittri reopened
reopened
- Author Contributor
Oops, sorry I got the issue mixed up, we still have trendlines to implement. We will re-evaluate this in the next dev metrics meeting.
- Author Contributor
We are no longer doing trendlines in this scope. Closing out. Awesome work @markglenfletcher @godfat
Also FYI @tpazitny since we no longer need to update the spreadsheet. Data at https://quality-dashboard.gitlap.com/groups/gitlab-org/time_to_close_bugs
- Mek Stittri closed
closed