Feature Requests

The current RelayProxy V2 key edit functionality allows users to accidentally assign production project keys to non-production environments and vice-versa. This can lead to security vulnerabilities and unexpected behavior. Can you implement environment demarcation during the edit phase of RelayProxy V2 keys. This would ensure that users can only assign keys to environments that match their intended purpose (production keys for production environments and non-production keys for non-production environments).

We require a dashboard that can generate reports on the usage and metrics of flags based on tagging. Currently, there is no designated field for Tagged Feature Flags to be displayed on the dashboard.

Display the targeting rules based on priority Check the attached image and the corresponding rule definition. The varition: "false" clause is sandwiched between the variation: "true" clauses and the UI gives no indication of the priority. While the priority set some how came up the way we want its easy to mess it up.

The current conditions only allow you to compare strings, for example: * Ends with * Contains I need operators like 'Greater than' and 'Less than' to compare numbers/floats. For example: My target has the attribute TaxRate, which ranges from 0 to 45. I need to add a condition in the Target Group to target customers whose TaxRate is greater than 20.

We have added a flag pipeline for their environments, but when we toggle the flag and hit the save button, a successful message appears while the pipeline is triggered and is waiting for approval. This would cause the team to believe that the flag was genuinely toggled. Is there a way we can display a notice that says “Waiting for approval” instead?

We want to switch on feature flag if release value (Integer) is greater than given number, in other words add option to create a Target Group based on some Integer attribute greater than Number provided. Currently greater than option is not available for integers.