Feature Requests

It appears that the parameters by which Harness moves their Recommendations to "accepted" status is too rigid. It doesn't appear to be observing the ticket's resolution field, and is looking at the status, so anything outside of the actual "Done" status won't be accepted We'd like Harness to either allow us to customize the acceptance criteria, or broaden the range.

I need metrics related to CI pipeline executions, specifically visibility on execution durations down to individual stages or steps. This would greatly assist in monitoring for regressions or improvements when changes are made to pipelines. Ideally, these metrics should be exposed using the Prometheus metrics format.

Hi team, good day, We would like to request the enable of SEI 2.0 for the Invex Account. Currently the default version of SEI is being used and would like to have access to the new model of SEI to use the new features. Sincerely, Izac Salazar.

We would like a method to take recommendations that are made with CCM and move them into the ignore List via API or through UI. We'd like to mark wildcards and for it to be able to process it. For example, all machines starting with windows-*

Currently, during the initialization step of our build pipeline, multiple health check failures occur before eventual success, resulting in a prolonged initialization of approximately 3.5 minutes. The initialization time on Harness Cloud is significantly longer than expected, and we anticipate a considerable reduction to improve overall build performance.

When actioning a recommendation Engineers often find the recommendation too harsh or contravenes a SaaS requirement, but they are able to implement a partial action of the recommendation and estimate their own more appropriate amount for the Savings $$$ figure. The integrations with Jira and SNow need to allow for the setting of the new amount when closing the ticket, populating the recommendation in Harness with the new estimated savings amount. They do not do this currently

Currently, S3 and GCS stores are not supported in additional manifest overrides. This feature request is to allow for having these sources for specifying the additional manifest overrides.

Add dark mode option to Gitness UI

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

As a potential workaround to https://ideas.harness.io/feature-request/p/enable-wiz-native-scanning-w-sto-in-cd-custom-stages , which is asking for a native STO Ingest Step in the Deploy Stage, it was suggested that it might be easier to make the STO ingest Step available in the Container Step Group. This is untested, so this request is to determine feasibility and ETA if possible.