Collapsable related issues/merge requests on feature flag details
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
With that addition of related merge requests #33615 and issues #26456 (closed), there is a potential these lists could become long and push the strategy information out of view.
Intended users
- Parker (Product Manager)
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Presley (Product Designer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
- Sam (Security Analyst)
- Dana (Data Analyst)
Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ -->
- Developers who create feature flags
- QA engineers enabling/disabling flags
- Release managers who want to control which features are released and to which customer base
- Support engineers that wish to release features to beta customers or test version to fix bugs for specific customers
Further details
Proposal
Move the related issue and merge request section into a collapsible section.
Permissions and Security
Documentation
Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Links / references
Edited by 🤖 GitLab Bot 🤖