Feature Requests

We currently track ramp-up schedules manually via Slack / Notion to make sure we increase exposure on specific dates. It’d be awesome if Split could integrate scheduling reminders directly: * Ideally via Slack (expanding on your current Slack integration offering) * The reminder could ping us with a notification and ask for manual approval before ramping. We'd still want the keep the decision-making manual while reducing the chance of missing timelines.

It would be great if we could schedule an automated rollout progression. For example, ramping from 50% to 100% over a 2-week period. If any issues come up, we’d still want the option to stop it manually. This would reduce manual overhead (and still give us the control).

It would be good for our team to be able to enforce standard naming conventions that make sense for our team

We have two mobile apps and we would like to use different projects for them.

For large accounts with many orgs and projects the FME settings page can be very large and hard to navigate. Being able to filter the FME settings page would help in administration and management of environments, permissions, sdk keys, traffic types, and so on

If you create a SemVer attribute in the dictionary, you should write: 1.0.1,2.0.2,3.0.3 And if you don't give a correct SemVer, the parser will fail and notify you to correct it. But if you this 1.0.1, 2.0.2, 3.0.3 And include a space before each version, there is no parsing helpful error about your problem. The submit button produces a red box that says something went wrong and you must go into the Developer Tools to find a reason.

Before you select a feature flag, the screen appears to be unrendered, which has confused some of the team members. It currently appears like a bug. It would be useful to at minimum offer some basic instructions like "select a flag".

IN multiple pipeline stages like - CI testing, STage testing, ADA testing we generate xml files for results. Can we integrate these to harness data to generate harness dashboards?

Customer would like to be able to more granularly monitor their MTKs. They would like to have self-service options for getting the visibility they see from the MTK reports that we can request and share with them. Ideally they would want to be able to see MTKs broken down by flags, by traffic types, and also be able to get notified when they reach their MTK entitlement. Customer implemented pooling to be able to better control their MTKs but they are still seeing higher than anticipated volumes which is leading to a decrease in their trust of the platform and ability to predict what their utilization would be.

On the same metric, want to be alerted for multiple thresholds (e.g. 5%, 10%, etc) and then also assign different stakeholders to be alerted per threshold identified. This allows them to prioritize and also identify how big the problem is.