2021-03-22 - Triage report for "group::optimize"

Hi, @ljlane @djensen @wortschi @dennis @jeremy @mikelong @npost

This is a group or stage level triage report that aims to summarize the feature proposals and bugs which have not been scheduled or triaged. For more information please refer to the handbook:

https://about.gitlab.com/handbook/engineering/quality/triage-operations/index.html#triage-reports

Scheduling the workload is a collaborative effort by the Product Managers and Engineering Managers for that group. Please work together to provide a best estimate on priority and milestone assignments. For each issue please:

Determine if the issue should be closed if it is no longer relevant or a duplicate.
If it is still relevant please assign either a best estimate versioned milestone, the %Backlog or the %Awaiting further demand milestone.
Specifically for ~bug, if there is no priority or clarity on a versioned milestone, please add a Priority label. Priority labels have an estimate SLO attached to them and help team members and the wider community understand roughly when it will be considered to be scheduled.
- https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#priority-labels
Once a milestone has been assigned please check off the box for that issue.
Please work with your team to complete the list by the due date set.

Feature Proposal Section

For the following feature proposals. Please either close or assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone.

Unscheduled ~feature with customer

gitlab-org/gitlab#323994 Mean time to merge calculations do not consider Draft/WIP states Category:Code Analytics, GitLab Premium, customer, devopsmanage, ~"feature", groupoptimize, sectiondev
gitlab-org/gitlab#294429 Value stream analytics > Not accessible via Keyboard Category:Value Stream Management, UX, accessibility, customer, devopsmanage, ~"feature", frontend, groupoptimize, sectiondev, workflowplanning breakdown
gitlab-org/gitlab#273806 Contribution analytics: combine the issues and MRs graphs customer, devopsmanage, ~"feature", groupoptimize, sectiondev, workflowproblem validation
gitlab-org/gitlab#263772 Feature Proposal: Option to Disable Group Level Activity Overview customer, devopsmanage, ~"feature", groupoptimize, sectiondev
gitlab-org/gitlab#218061 Show stage or job duration in the overall CI/CD statistics customer, devopsmanage, ~"feature", groupoptimize, sectiondev
gitlab-org/gitlab#209328 Provide ability to configure Working Hours for Value Stream Analytics customer, devopsmanage, ~"feature", groupoptimize, sectiondev, workflowproblem validation

Unscheduled ~feature (non-customer)

Unscheduled UX Debt Issues

gitlab-org/gitlab#322136 (closed) [VSA] Fix stage time scatterplot Category:Value Stream Management, UX, UX debt, devopsmanage, ~"feature", groupoptimize, sectiondev, workflowplanning breakdown
gitlab-org/gitlab#322135 [VSA] Change days to completion to lead time and cycle time Category:Value Stream Management, UX, UX debt, devopsmanage, ~"feature", groupoptimize, sectiondev, workflowplanning breakdown
gitlab-org/gitlab#322126 (closed) [VSA] Remove days to completion scatterplot dropdown Category:Value Stream Management, UX, UX debt, devopsmanage, ~"feature", groupoptimize, sectiondev, workflowplanning breakdown
gitlab-org/gitlab#246493 (closed) Remove vertical value stream tiles UX, UX FY21-Q4, UX debt, devopsmanage, ~"feature", featureenhancement, frontend, groupoptimize, priority2, sectiondev, workflowplanning breakdown
gitlab-org/gitlab#204726 (closed) Contribution analytics: chart zoom usability UX, UX debt, devopsmanage, groupoptimize, sectiondev

Bug Section

For the following bugs. Please either close or assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone and ensure that a priority label is set.

Engineering Managers: Please add a severity label for those issues without one
Product Designers: Please add a severity label to UX ~bug issues without one

Heatmap for all bugs

Bugs for their priority and severity label are counted here. Every bug should have severity and priority labels applied. Please take a look at the bugs which fall into the columns indicating that the priority or severity labels are currently missing.

	severity3	severity4
priority1	0	0
priority2	0	0
priority3	3	1
priority4	0	3
No priority	9	5

Heatmap for customer bugs

	severity3	severity4
priority1	0	0
priority2	0	0
priority3	1	0
priority4	0	0
No priority	0	1

Unscheduled frontend ~bug with customer

gitlab-org/gitlab#295674 (closed) Y axis of "Duration for last 30 commits" has unclear unit of measure 'm' ~"Accepting merge requests", ~"bug", customer, devopsmanage, frontend, groupoptimize, sectiondev, severity4

Unscheduled frontend ~bug (non-customer)

gitlab-org/gitlab#324673 (closed) Group-level VSA - Inconsitent value_stream query parameter backend, ~"bug", devopsmanage, frontend, groupoptimize, sectiondev, severity3
gitlab-org/gitlab#321610 [VSA] Labels should persist with new date range or page refresh ~"bug", devopsmanage, frontend, groupoptimize, sectiondev, severity4, workflowsolution validation
gitlab-org/gitlab#291047 (closed) Repository -> Contributors | RangeTrackbar unexpected behavior ~"bug", devopsmanage, frontend, graphs, groupoptimize, sectiondev, severity3
gitlab-org/gitlab#266979 (closed) FIx Analytics dropdown date range picker overflow ~"bug", devopsmanage, frontend, groupoptimize, priority4, sectiondev, severity4
gitlab-org/gitlab#246790 (closed) y-axis in Merge Request Analytics table displays 500m label Next Up, ~"bug", devopsmanage, frontend, groupoptimize, priority4, sectiondev, severity4, workflowplanning breakdown
gitlab-org/gitlab#219933 (closed) Productivity Analytics: Trendline chart not loading because 'status' undefined Next Up, ~"bug", devopsmanage, frontend, groupoptimize, missed:13.2, missed:13.3, missed:13.4, missed:13.5, priority3, sectiondev, severity3, workflowready for development
gitlab-org/gitlab#216799 (closed) VSA: weird aggregation in duration chart Category:Value Stream Management, ~"bug", devopsmanage, frontend, groupoptimize, sectiondev, severity3

Unscheduled ~bug with customer

gitlab-org/gitlab#229716 (closed) Group-level Productivity Analytics do not show metrics for nested projects in subgroups Support Team Contributions, ~"bug", customer, devopsmanage, groupoptimize, priority3, sectiondev, severity3

Unscheduled ~bug (non-customer)

gitlab-org/gitlab#323704 (closed) Inconsistent Data in Insights Graphs ~"bug", devopsmanage, groupoptimize, insights, sectiondev, severity3
gitlab-org/gitlab#229198 (closed) Total Contributions column within the Contribution Analytics does not always equal the sum of the other columns ~"Accepting merge requests", Next Up, ~"bug", devopsmanage, groupoptimize, sectiondev, severity4, workflowscheduling
gitlab-org/gitlab#197161 Improve documentation on how to get total time computation in cycle analytics ~"bug", devopsmanage, documentation, groupoptimize, sectiondev, severity3

Open Quarantined Flaky Specs Issues

gitlab-org/gitlab#273045 (closed) Flaky test './ee/spec/features/groups/analytics/cycle_analytics/customizable_cycle_analytics_spec.rb[1:3:2:1:1:2:3]' # Customizable Group Value Stream Analytics with a group with a custom stage created behaves like can edit custom stages Edit stage form Category:Value Stream Management, Engineering Productivity, devopsmanage, failureflaky-test, groupoptimize, ~"quarantined test", sectiondev, test
gitlab-org/gitlab#250638 (closed) Flaky test in ee/spec/features/analytics/code_analytics_spec.rb | CodeReviewAnalytics Filtered Search when the "new search" feature is disabled with merge_requests filters the list of merge requests Category:Code Analytics, Engineering Productivity, Quality, analytics, devopsmanage, failureflaky-test, groupoptimize, needs investigation, ~"quarantined test", sectiondev, test
gitlab-org/gitlab#216745 (closed) './ee/spec/features/analytics/cycle_analytics/cycle_analytics_spec.rb[1:9:1:1:2:1:1:2]' Category:Code Analytics, Engineering Productivity, analytics, devopsmanage, failureflaky-test, groupoptimize, priority2, ~"quarantined test", sectiondev, severity2

This is a group level triage report that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook:

https://about.gitlab.com/handbook/engineering/quality/triage-operations/index.html#triage-reports

If assignees or people mentioned in this individual triage report need to be amended, please edit group-definition.yml.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information