VSA settings: [UX] Value Stream inheritance within the group hierarchy
Release notes
Problem to solve
Organizations want to streamline their development processes. To do so, they will likely define the same value streams and value stream stages for subgroups and projects.
Currently, to have the same value stream (with stages) for subgroups and projects, the user will need to create them manually on each namespace resource (Group, ProjectNamespace). This can create significant admin overhead; automation is currently not possible because we don't provide an API for creating value streams and stages.
See source issue: VSA settings: [BE] Value Stream inheritance wit... (#409655)
Proposal
Allow selecting value streams from parent groups
Example:
- Top level group:
gitlab-org- Defines the standard workflow stages in the "Main" value stream, based on the `workflow´ labels.
- Project:
gitlab-org/gitlab- Defines a custom value stream based on the
database::reviewedanddatabase::approvedlabels to measure the DB review process (custom process for this specific project)
- Defines a custom value stream based on the
When the user navigates to the gitlab-org/gitlab project, the user would see both value streams. The value streams would be already filtered down to the current project.
Intended users
Design considerations
- Provide the possibility to disable the inheritance
- Value streams rate limits: Limit is applied on the group/project level. In case you have 40 value streams on the top-level and another 40 in a sub-group, we would render 80 value streams when opening the subgroup or a project in the subgroup. How will this affect Alert when VSA application limits are reached (#416580)
- Restrict the option to modified from a lower-level the a top-level value stream.
- It would be nice to show the name of the value stream with the group name where it was inherited from. We could even add some sort of separator where we show the direct value streams on top and below them we would list the inherited value streams. This is related to VSA settings: [FE] Add selected projects per va... (#381006).
Feature Usage Metrics
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.