Feature Requests

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.

Please check my Jira Review to understand my issue with the extremely limited Jira plugin you provide: https://marketplace.atlassian.com/apps/1227514/com.harness.ff.plugin.jira?hosting=cloud&tab=reviews Thanks Marco Borm

Need the access to capture the analytics for the feature flag via API.

In Optimizely, flags have "variables" inside them. This allows us to keep logically related values of a flag inside a flag. Here flag functions as a container. The major benefit of this is that for a target group, we can see all the "variables" on one page. In Harness, we would have to define separate flags for all these aspects of a single feature. At one time, we would only be able to look at one flag's value. The request is to make it easier to group flags of an associated feature, and ideally, make it easier to view these related flag values.

Creating a ticket as advised from Ethan Jones. Details: I would be great if we could check if a FF exists in Harness. That way we could fallback to our legacy mode when the FF is not found. So would it be possible for Harness to add a public method for determining if a flag exists? The targeting or default value doesn't matter. It would be a public method on client. Something like: def exists?(flag) @repository.get_flag(flag) != nil end (found this from the evaluator.rb your inner_client.rb. uses and looks like it may do the trick if exposed as a public API) (edited)