Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 35,750
    • Issues 35,750
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,203
    • Merge Requests 1,203
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #262070

Closed
Open
Opened Oct 05, 2020 by Dan Jensen@djensenDeveloper

[VSA] "Days to completion" chart should not use totals

Problem to solve

The "Days to completion" scatterplot was added to group-level Value Stream Analytics under #12078 (closed). Currently this chart displays the total time spent in the given stage by all items that completed the stage on each date. Using total seems fundamentally flawed.

If multiple items coincidentally exit the given stage on the same date, the value for that date will tend to be much higher than other values. However, that high value does not indicate high or low functioning - in fact it is probably useless information because it cannot be compared to the other data points.

More generally, this chart was originally described as, "Essentially, the added value of all stages in Cycle Analytics for that date." However, time does not equal value. In fact, it is obviously more valuable to deliver the same work in less time. So totals are possibly even counterproductive.

Proposal

  • The "Days to completion" scatterplot should display average time to complete the stage (not total/combined time).
  • This should be reflected in the documentation per !43446 (comment 424939811).

Related links

  • In #249803, @gweaver said: "I don't really understand how this is being calculated or what it is telling me."
Edited Oct 06, 2020 by Dan Jensen
Assignee
Assign to
13.11
Milestone
13.11
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab#262070