Remove `recaptcha_on_top_level_group_creation`
Why are we doing this work?
The recaptcha_on_top_level_group_creation feature flag is not enabled in any environment.
Additionally, there is no clear documentation or validation confirming that the implementation is complete, tested, or ready for release.
Given this uncertainty, enabling the feature now would pose unnecessary risk.
To reduce maintenance overhead and eliminate unused code, we will remove the code gated by this feature flag.
- Risk: High if we release it but Low if we remove it.
- SaaS: Yes
- Self-Managed: Probably designed for SaaS but it might work in self-managed.
If we remove this we need to check with an adult to make sure that it's okay.
- Do we have any contracts with customers to keep this feature?
| chatops | dev | staging | staging-ref | production |
|---|---|---|---|---|
/chatops run feature get recaptcha_on_top_level_group_creation --dev --staging --staging-ref --production |
does not exist | does not exist | does not exist | does not exist |
Relevant links
- Chatops
- Definition
- Rollout Issue: None
- Feature issue: None
- Introduced By
- [FF removal] Default enabled and remove recaptc... (#388192) • Unassigned • Backlog
- [Feature flag] Evaluate need for `recaptcha_on_... (#441663 - closed) • Jay • Backlog
Implementation plan
-
Delete code that is gated behind the feature flag. -
Create database migrations to delete related tables. -
Delete documentation -
Delete feature flag YAML definition -
Close rollout issue
Verification steps
-
The YAML definition for the feature flag is deleted -
The associated database tables are deleted from the database -
The associated code that was gated by the feature flag is deleted -
The feature flag is removed from the dev, staging, staging-ref and production environments.
Edited by mo khan