Make sure the documentation and code agree on a consistent set of feature toggles
Requirements to Consider
Consider how we can prevent drift between the documentation and code in the future.
Consider whether we need to periodically check the feature toggles to ensure consistency.
Tasks
Answer the following questions:
Which feature toggles existing in each environment?
Which feature toggles are not listed in the documentation?
Time Box
_ hours
Definition of Done
Tasks are complete
Research and recommendations are documented in this ticket
How to configure this issue
[ ] Attached to an Epic (what body of work is this a part of?)
[ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
Background/Request
We seem to have an inconsistent set of feature toggles. Here are the different places where they are defined:
Documentation:
Flipper UI:
Code:
Goal
Make sure the documentation and code agree on a consistent set of feature toggles
Requirements to Consider
Tasks
Time Box
_ hours
Definition of Done
How to configure this issue
backend
,frontend
,devops
,design
,research
,product
,ia
,qa
,analytics
,contact center
,research
,accessibility
,content
)