Feature Requests

Multi-Select option should be enabled. As per the documentation below it is mentioned to raise a service request with the Harness Support team for enabling the option. https://developer.harness.io/docs/platform/variables-and-expressions/runtime-input-usage#allow-multi-selection-and-single-selection

Comments and split status are missing from the integration. Ven would expect this to be visible in the notification messages sent to Slack. Otherwise the base use case does seem to work, almost apples to apples comparison with the existing LaunchDarkly Slack app. Also, the team is concerned about if the Slack integration will be worked on further or not. This integration is important to them as they use Slack heavily for comms.

Add support for Valkey (drop-in Redis replacement)

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.