Feature Requests

Before you select a feature flag, the screen appears to be unrendered, which has confused some of the team members. It currently appears like a bug. It would be useful to at minimum offer some basic instructions like "select a flag".

We want to set up alerts to know if builds are queueing up in absence of infra availability or if certain pipelines are taking too long or getting stuck etc We want to extract this data from Harness and send it to Splunk so that can be a one stop shop for all metrics + alerting.

In SEI 2.0, you cannot change the structure of an existing configured organisation tree. The only option is to create a new tree, but doing so will require reconfiguring the settings, adding manual effort, and causing unnecessary toil for the customer.

I want to be easily be able to toggle a step on/off without having to set a condition. I could potentially have a condition already set on the Step and just want to disable it without removing the condition. Another thing with the current functionality is it requires many clicks + typing in order to disable a step. This should be a simple one click + save.

Many reports such as coverage, linters, unit tests from various languages, etc use proprietary HTML reports. Harness enables you to upload these reports as artifacts to S3 or similar, but it does not support HTML reports natively. I would like to see this feature make it to Harness similar to https://plugins.jenkins.io/htmlpublisher/ to support additional quality and build reports

Description: The CI_COMMON_ENV_POD feature flag reduces pod.yaml size by storing Harness internal environment variables in a shared ConfigMap. However, custom stage variables are still duplicated across every step container, even when not referenced by that step. Request: Extend this optimization to include custom stage variables in the common ConfigMap, and only inject variables into steps that actually use them. This would significantly reduce pod.yaml size for pipelines with many steps and stage variables, helping prevent "etcdserver: request is too large" failures in Kubernetes environments.

Observability metric for the ssca-manager service is not supported in SMP

Add dark mode option to Gitness UI

RSPM rules do not work for configs that are defined at github account and org level.

We'd like the ability to run the local runner as a service instead of just executing it directly while in the machine. This is to help improve uptime in case the runner goes down for any reason so we don't have to manually SSH into the machine and reboot the runner every time.