Feature Requests

Goal is to implement Checksum validation in CI for already executed changesets. DBSchema Test and Preview in CI using DBSchema/dbinstance is counted against resource constraint which in turn blocks CD using same DBSchema/dbinstance. Feature Request is to have lockfree/resource constraint free native method to perform checksum validation in CI

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

Summary The current Harness UI fails to provide adequate visibility for policy evaluations configured with "warn and continue" status. Pipeline steps with policy warnings still display a green checkmark, making warnings effectively invisible during normal pipeline execution. Detailed Description We have configured our development build pipelines with a policy set intended to evaluate Software Composition Analysis findings but allow the pipeline to continue rather than fail on policy violations. However, we've encountered a significant usability issue: When a policy evaluation results in warnings (with "warn and continue" configuration), the pipeline step still displays with a green checkmark in the UI The only way to discover that warnings occurred is to manually dig into the "output" tab of the specific pipeline step This makes policy warnings effectively invisible during normal workflow, defeating the purpose of having warnings

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.

JUnit is changing to a new reporting format that is supposedly language agnostic, can harness please add support for open test formatted reports in it's test reports as well? https://github.com/ota4j-team/open-test-reporting

I want to use the AWS connector permission in S3 cache/restore step to access S3 however S3 cache/restore step is currently using the permission on the stage infrastructure connector. Expected behavior: When we specify an AWS connector in the S3 cache/restore step, we need to use the permission of AWS connector to access S3 rather than using the permissions defined in the stage infrastructure connector Observed behavior: In order to access S3 currently we don't use the permission of AWS connector configured in the S3 cache/restore step instead we use the permissions of stage infrastructure connector

Similar to the CD module user would like to have the Approval as a CI step.

We were going through this feature to visualize CPU and memory utilization metrics on Cloud builds: https://developer.harness.io/docs/continuous-integration/use-ci/set-up-build-infrastructure/view-resource-utilization-metrics/ Is there a plan to provide the same feature on self-managed build infrastructures? Any ETA for this feature?

As discussed with the Harness team - Hitesh, Karan, Max - at FinOps X 2026 I am submitting a PFR request for a connector integration with OCI. The primary use case is to pull down the Oracle Exadata CUR with daily cost usage. Sharing details and summaries from our discussion. Please clarify anything I misspoke here. Knowns: -Per Harness team, currently supported FOCUS spec is v1.1. No other FOCUS spec is supported. -Per Oracle Billing team, Exadata CUR is available GA w/ v1.0 and has a private preview for v1.3. Unknowns: FOCUS backwards compatibility v1.1 -> v1.0 Next Steps: ELVH placed a ticket with Oracle to understand CUR FOCUS spec availability from OCI. Harness team to share further details/reqs on developing the integration with OCI billing data