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 34,902
    • Issues 34,902
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,220
    • Merge Requests 1,220
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • 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
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #35823

Closed
Open
Opened Nov 07, 2019 by Ezekiel Kigbo@ekigbo🚴🏾Maintainer12 of 14 tasks completed12/14 tasks

Customizable value stream analytics: general availability

This issue coordinates outstanding bugs and steps related to making customizable cycle analytics generally available. A recap of this feature:

Cycle Analytics comes with out-of-the-box definitions of a value stream, but organizations may have opinionated workflows. In order to introduce more flexibility into Cycle Analytics, we're introducing customizability into this feature:

Object type Start event Start parameter, Stop enabled Filled out
ca-custom-stages__add--object-type ca-custom-stages__add--start-event ca-custom-stages__add--start-event-selected ca-custom-stages__add--filled-out

A comprehensive list of start/end trigger events can be found here.

Launch checklist

  • Customizable cycle analytics MVP
  • Fetch stage data and medians from new endpoint
  • Restoring default stages (if they're hidden)
  • Excessive select events triggering when viewing options
  • Adding custom cycle analytics stage reorders default stages
  • Stage table fixed height UI polish
  • Consolidate cycle analytics URLs
  • Generate stages with label information from fixtures
  • Gracefully handle 4xx errors

Post launch

  • Re-ordering cycle analytics stages
  • Filter layout at sizes between 768px - 996px UI polish
  • Investigate slow jest tests + use more shallow rendering particularly base_spec and custom_stage_form_spec : moved to &2434
  • Ensure default stage names can not be used for custom stages
  • Truncate long value stream analytics names in the stage list
Edited Apr 01, 2020 by Ezekiel Kigbo
Assignee
Assign to
12.9
Milestone
12.9 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab#35823