Feature Requests

The Jira integration is currently too limited, and they'd like to be able to configure it for more than one environment at once. They use Jira for everything, so being able to track all environments in Jira would be useful.

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.

Customer is interested in reducing the impact of a poor-performing variant and choosing a winning variant sooner rather than later.

The team would like to be able to enforce tags (e.g. require at least one tag when creating flags) and also edit/manage tags (e.g. pre-populate tags in admin settings for team to use). Due to the # of flags they plan to use, tags will be the key way to keep track of them.

Typescript app is browser-based and they want a level of abstraction. They want to use OpenFeature, so in this case, the web provider is high priority for this implementation. They've also been looking into the value/effort of having an implementation of current in-house feature flag system so that we could abstract it as well behind an open feature provider and eventually ease the migration from one to the other with minimal changes to consumers on client-side. Not a blocker for implementation yet, but could become a blocker.

Customer is requesting updates to the OpenFeature Web Provider. Their ideal scenario is to use the Split Browser SDK and the OpenFeature Web Provider. The team has a centralized platform (Breeze) that other teams make API calls to as opposed to hitting the SDKs directly. They are evaluating moving to OpenFeature to help more teams use feature flags and be vendor agnostic.

Team wants to be able to restrict editing AND require approval, for more security.

Policy as code - guardrails on how fast you can enable features in the platform

Really like - Code references - where FF is in code like LD has today

For the customer one of the key selling points of FME is the integration with CD. Can they have a dashboard of some kind? - One view that shows us the deployments that have happened, flags that have changed states recently? - Unified view exists today for all other modules including CD but we don't have one for FME. Would be good to integrate FME related things within the Unified View that highlights what feature flags have changed recently, pushed to production etc. Some great examples to have: FME Metrics for Unified View Recent Activity Recent flag state changes (who, what, when) Flags modified in last X hours/days Current Flag Impact Flags currently serving non-default treatments Flags active in production Experimentation Active experiments (status, goal progress) Conversion metrics (uplift, significance) Deployments + Flag Toggles Unified timeline view of deployments + flag changes Correlation for RCA/postmortem Ownership & Hygiene Flags by owner Orphaned/stale flags SDK evaluation counts Categorization Flags by tag/type (e.g. kill-switch, experiment) Short-lived vs long-lived Cleanup candidates