Feature Requests

When selecting individual targets for a feature flag, the identifier key of the target is shown. This key will typically be some durable key, mapping from maybe a monotonically incrementing database value (surrogate key) or some other globally unique identifier (GUID, ULID, SnowflakeId). While identifying by key is good, managing by key only does not seem very user friendly. Ideally, we'd be able to display some other friendly field alongside the id so that our product people can add and manage the targets without having to do an id lookup.

Currently Harness is allowing only single select from drop-down list, I have a usecase to select multi-select from drop-down list. Could you please enable feature flag for multi-select functionality in our harness? PIE_MULTISELECT_AND_COMMA_IN_ALLOWED_VALUES

In SplitIo, when selecting individual targets for a feature flag or building a segment, identities of the target traffic type can only be searched by Case-Sensitive Startswith, causing friction when configuring feature flags. e.g. For the following identity "1" with a friendly name attribute of "ABC", searching for the identity "1" by "ABC" returns "1", but searching by "abc" (note lowercase) returns no matching identities. We are requesting that identity search have the capability to do a Case-Insensitive Contains since that's more intuitive to our Product Management user group, enabling them to more easily migrate from our in-house feature flag tool to SplitIo.

Requesting Git sync of the feature flags in a single project to the different microservice repositories. Feature flags store all flags in a single project under one single repository, so there is not an easy way to separate them and sync them back to multiple microservice repositories without updating our Harness account structure.

We have a similar requirement to: https://ideas.harness.io/feature-request/p/show-feature-flags-affecting-harness-inside-the-harness-platform Currently the only way we can understand what feature flags are applied to an account is to use dev tools in edge or chrome and capture the evaluations response from a page refresh. We would like to have a supported api call that allows us to get the feature flags as part of an automated report solution. We would also want the ability to view them within the UI under the account settings pages.

Please turn on CCM_BUDGET_CASCADES in https://coles-npe1.harness.io asap

Enable Feature Flag PL_CUSTOM_BANNERS on Harness account https://app3.harness.io/ng/account/kiIG5wEzQPGnwy9FGv0jOw

Enable Feature Flag PL_CUSTOM_BANNERS on Harness account https://app3.harness.io/ng/account/kiIG5wEzQPGnwy9FGv0jOw

We would like to use AWS Redis serverless solution with Feature Flag proxy. However, serverless only supports TLS connectivity. It would be nice if that was was a possibility.

For any given Harness instance we would like to see the status of Feature Flags affecting that account in a Harness UI, so we don't have to rely on Customer Support to tell us the status of feature flags which impact the way the Harness platform operates.