Issues Analytics: Add "Issues closed" - total issues closed
Release notes
Introducing Enhanced "Issues Analytics" for Deeper Project Insights!
We've added a new metric - "Issues closed" to the "Issues Analytics" report to help software leaders to track the total number of resolved issues over a specific period. With this valuable addition, Gitlab users can now gain insights into trends associated with their projects and improve the overall turn-around time and value delivered to their customers.
The "Issues Analytics" visualize via bar the number of issues for each month, with a default time span of 13 months, and can be access via drill-down from Value Streams Dashboard.
Problem to solve
- Issues analytics only shows opened issues - this information isn't too valuable by itself.
- Users want to see total number of issues superimposed with issue activity. This is one of the "Lifecycle metrics".
- Issues analytics is one of the drill-down from Value Streams Dashboard.
Intended users
Proposal
Adding to Issues Analytics:
-
Group-level & Project-level. -
Remove dataZoom
component from chart -
Adding new Y axis bars
for "Issues closed", in addition to the current "Issues created". -
As not all filters are available on this new endpoint, introduce the change behind a feature flag and reduce the selectable labels to those which are supported when the feature flag is enabled. -
Adding tooltip interaction (Example). -
Issues closed - the number of issues closed each month for GitLab Ultimate only. Issues created, same as today for GitLab Premium GitLab Ultimate. Reasoning. - the data should be available on the GraphQL API with the usual restrictions (maximum 10K rows, premium or ultimate):
query {
group(fullPath: "gitlab-org") {
flowMetrics {
issuesCompletedCount(from: "2022-01-01", to: "2022-02-01") {
unit
value
}
}
}
}
Design source
Customer feedback
Related- Issue analytics: Generate graph of issues closed (#389093 - closed)
- #381787 (comment 1248653456)
- #196542 (closed)
- Dogfooding opportunity - https://app.periscopedata.com/app/gitlab/1019503/Reliability-Team-Dashboard
Next iterations
- Issues Analytics: Add "Total open issues" - ope... (#417435)
- VSD drilldown links - Inherit the labels from t... (#419493 - closed)
- Issues Analytics: Add pagination to table (#351552)
old Links / references
Click to expand
- Related to Q3 Dogfooding OKR
Technical notes
You need to Feature.enable(:new_issues_analytics_chart_data)
in rails console to get new data format for issues analytics chart. See !46444 (merged) for details
- Add total open (accumulated) issues to chart in project-level issues analytics, see discussion here
- Requires this component