Feature Requests

Today the web editor shows a DIFF change for feature flags when staging a change, but the CR API does not provide the same. Request is to provide DIFF changes for FME CRs either via existing CR API, or a new one.

Customer would like to be able to manage the tags that they have in their account and delete any that are no longer needed or were created by mistake.

Investigate and remove the current dependency on Account Admin / all-resources scope for the ServiceNow integration's service account, so it can be scoped down (e.g., to the environment(s) it's actually used with) without breaking the change-request creation/approval flow, and ideally without requiring the account-admin role at all.

Customer would like to use policies for approval assignments. They would be able to associate feature flag tags with specific approver groups, so that any flag with a given tag automatically inherits the approval policy associated with that tag.

Environments on the flag view are in no particular order making them hard to manage. On most other pages, environments are listed alphabetically which seems reasonable to me but they don't flow like we think about feature management. Most of the time, we're enabling in a lower env then elevating incrementally through environments. I want the ability to choose the display order. In a perfect world too, I want to initialized environments shown on top in my specified order while uninitialized environments are shown below in order to keep flags clean and easy to manage.

Feature flags should have an expiration date that can be configured. These should give information to the owner or other optional configured users when the flag is approaching or past the expiration date, and optionally allow automations upon reaching expiration.

Give admins control over how the "ready to clean up" designation is determined on the Rollout Board. Today this is a fixed rule: flags untouched for 100+ days in a specific set of statuses (e.g. ramping, removed from code, released, killed) get flagged as ready to clean up, with no way to adjust it. Requested: Configurable day threshold (not hardcoded to 100 — e.g. some teams want 180 days). Configurable which statuses count toward the designation (ability to include/exclude specific statuses, such as excluding permanent flags). More broadly: the ability to build a custom filter/button rather than relying on one fixed rule.

Customer would like to allow developers to create feature flags directly from a template that includes a specific segment. Currently, to do this, they need every developer to do this action manually and there is no workaround for it right now instead of using the APIs. They want every developer to be self-sufficient and be able to create flags directly. Statsig offers this out of the box today.

FME tags can be created when editing a feature flag, but there seems to be no way to edit or remove them. Either we need a tag management interface or the tags need to be automatically removed when no feature flag is using them.

Grant admins universal permission to approve, deny, or cancel any pending change request.