Feature Requests

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

Enhance connectors to use account level variable for endpoint url value rather than string value. Use case: If we need to switch vault url from one data center to another data center, change at the account level variable and make it seamless rather update 2000+ connectors through api and might take couple of hours to switch to all 2000 apps.

Add dark mode option to Gitness UI

Add Rapid7 for Orchestration, Ingestion as supported External Scanner https://developer.harness.io/docs/security-testing-orchestration/sto-techref-category/security-step-settings-reference

Currently when we perform STO scan, the STO scan page shows RAW data, which contains important information like root package name etc. But when viewing the same result in the custom dashboard, these fields present in raw data are not available. Please add support for it.

We need a comment section for each occurrence of an issue. This will allow us to provide our analysis, especially in the case of a true positive, for future reference. Having the option to add comments to a specific occurrence would be very helpful for developers or testers to better understand the context whenever they revisit the issue.

Today in SEI 1.0 we don’t have an out-of-the-box way to support this use case. It would require setting up two separate integrations but that approach doesn’t scale well — especially if each team has its own variation. The request here is to make the story points mapping available as a team setting rather than an integration-level configuration.

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-*