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 |
|---|---|---|---|
 |
 |
 |
 |
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: moved to &2434base_specandcustom_stage_form_spec - Ensure default stage names can not be used for custom stages
- Truncate long value stream analytics names in the stage list