Manage Feature Flags
We encourage engineers to add feature flags in many scenarios in order to safely roll out some of our work - but when the feature flags stay in the codebase over a period of time, we accrue tech debt and are never able to release the work that we have already done. The more stale feature flags left in the system, the less customer value we have provided.
Manage has 60+ feature flags in the codebase that are older than 2 months. A recent conversation has surfaced around whether or not we are taking action on the monthly feature flag reports, which has raised my own questions.
| Group | # of Flags | Notes |
|---|---|---|
| Auth | 30 | - Some are under "manage::access", "access" and "authentication and authorization" - Most of them are disabled, a total of 24 |
| Workspace | 14 | - All of them are disabled. |
| Import | 12 | - Some are under "import" and others are under "group::import" - 7 of them have been default enabled for ~2 years (I would think these are safe to remove by now) |
| Integrations | 5 | - All of them are disabled |
Here is a Google Sheet output of the Sisense data in case it is easier to filter
- Are you all already aware of these? Are there any improvements we need to make to the triage issues for them to have more of an impact?
- What are the primary reasons why so many are disabled for this amount of time?
- What support do you need in order to address these flags?
- Is there a portion of these that can be removed (default enabled or deleted) easily?