Design: Create vision for Feature Flags as an issue type
Release notes
Problem to solve
Create a design to articulate the long term vision of the "Feature Flag as an issue type" epic.
"As a feature flag user I want to be able to create a feature flag and link MRs, issues to it, easily sort and filter and have discussions around the flag."
Intended users
- Parker (Product Manager)
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
- Sam (Security Analyst)
- Rachel (Release Manager)
User experience goal
Create an easy and natural way to manage feature flags, including connecting to issues, MRs, epics, assigning DRIs, and opening up discussions.
The solution should serve as a full detail view related to a feature flag.
Proposal
Create a new interface for feature flags, starting with the detail view, to enable users to manage and coordinate feature flags individually and together as a team.
Here is a video walkthrough and the figma file
| Feature Flag List View |
|---|
 |
| Feature Flag Detail Overview |
|---|
 |
| Feature Flag Detail Strategy | Feature Flag Detail Code References |
|---|---|
 |
 |
Further details
A few open questions to be explored after solution validation and as part of the issue breakdown:
- How does the feature-flag level toggle work for individual strategies?
- How does the "Open cleanup Mr" work?
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
We should communicate with Plan/Create/Monitor around detail types, etc.