Feature Requests

Currently, only the requester can modify or cancel a scheduled change. This creates operational risk if that person is unavailable, as other team members cannot intervene to prevent or adjust a rollout.

Create a centralized UI dashboard within Harness to view and manage enabled Feature Flags across the platform. Currently, users must call APIs to discover which feature flags are active. A UI would provide visibility, searchability, and ease of management for feature flag configurations, improving operational efficiency and troubleshooting capabilities.

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 enable this feature flag for us to be able to download the logs using the API. https://developer.harness.io/docs/platform/pipelines/executions-and-logs/download-logs/#download-logs-with-simplified-log-key

My project has a lot of tags. When I select a tag it is easy to get the UI in such a state that it is hard to know what tags are already selected. Perhaps I want to deselect one of the previously selected tags. The only way to do this is to remember what tags I previously selected and filter to find them. It would be nice if the UI always put selected tags on top or had some other way to see and deselect tags that are already selected.

Support feature tracking and impressions from using the .NET SDK In DataDog, there's a Feature Flag Tracking dashboard under the Real User Monitoring feature set that has Split.io integrations to track feature flags based on user impressions. However, the current integration only provides tracking for client-side impressions (Javascript). The current primary usage of feature flags for our organization comes from server-side feature management using the .NET SDK (we are primarily an .NET/C# shop). Being able to send feature flag details and impressions to DataDog from the .NET SDK would be helpful, or else we would have to write our own custom integration. https://docs.datadoghq.com/integrations/split-rum/

lite-engine container gets OOM killed by default( with 100MB limit), If we disable the feature flag CI_CONSERVATIVE_K8_RESOURCE_LIMITS, it sets the lite-engine resource request to the max of any of the step's resource limits. This reserves unnecessary resources for lite-engine. Provide a way to set the lite-engine resource per pipeline or per project level or account level

pls enable CI_REMOTE_DEBUG flag

I would like to experiment with using BuildX on K8s when running a CI build in Harness Harness BuildAndPushDockerRegistry stage type in favor of running Docker-in-Docker due to the limitations of Kaniko but now that there is a feature flag to enable BuildX for BuildAndPushDockerRegistry, I would like to explore its usage if possible.

this is a test FR