Date of slack thread: 4/8/24
Anonymous: Hi! We are trying to clean up all of our in progress feature flags that are actually launched at 100% following the documentation here. Since we are an app, these feature flags are gated on app version. Does “launching” a feature flag (setting the status to “launched”) respect the rules on the feature flag? My concern is I don’t want users on an old app version seeing the new feature that is launched at 100% on a newer app version.
Matt Garnes (Statsig): Hi! For that use case, which is a common and important one, you will need to not use the launch feature and instead you can “mark as permanent” so that you can filter for these and you won’t be notified that it is old/stale when you need to keep it around forever.
It’s definitely a limitation that our “launch” functionality doesn’t let you categorize a gate that is not out to literally 100% but effectively as launched as it will ever be, as such. We will keep this in mind as we evolve our gates lifecycle features!