Feature Requests

我正在使用 Harness NextGen SaaS（ app.harness.io ），按照官方安装向导生成了 Docker 命令，但 Delegate 启动后反复报错：com.nimbusds.jose.JOSEException: The A128GCM encryption method or key size is not supported by the JWE encrypter: Supported methods: [XC20P, A256GCM, A128CBC-HS256, A128CBC+HS256]

Failures in Harness are not categorized today. There is no cross-team visibility when multiple teams hit the same root cause simultaneously. 29% of survey respondents (Feb 2026) rate root cause identification as POOR. Slack support data shows SonarQube and JFrog errors hitting multiple orgs with no cross-team pattern surfaced — every team re-discovers the same issue independently. We need: — Automatic failure categorization (infra, test, compile, config, external dependency) — Customer-managed knowledge base: regex rules → known causes → remediation steps — Failure trending and flaky test detection across builds — MTTR tracking per failure category — Cross-build correlation: surface when N pipelines fail on the same root cause The knowledge base must be editable by the customer (DPE) without requiring Harness involvement. Business value Eliminates repeated ticket ping-pong. Target: MTTR from 2–4 hours to under 15 min for categorized failure types.

Harness logs are per-step only today. There is no cross-step search, no correlation with infrastructure events, and no way to download a diagnostic bundle for escalation. Developers navigate: execution view → step logs → delegate page → manual correlation across separate screens. Slack data: cryptic errors with zero context requiring multi-hop investigation to diagnose. We need: — Structured JSON log output with severity classification — Full-text search across all steps in an execution — Log correlation with system events (delegate restart, pod eviction, OOM kill) — Export to S3 / GCS / ELK / Splunk for teams with existing log infrastructure — One-click diagnostic bundle download: all step logs, infra events, delegate data packaged for escalation This pairs with FR-9 (semantic log level classification) and FR-1 (resource metrics). Business value Eliminates multi-hop diagnosis. Enables self-service root cause analysis without opening a support ticket.

Could you enable the CI_CPU_MEMORY_INSIGHTS for our instance please?

backstage.io supports the extension of the model ( https://backstage.io/docs/features/software-catalog/extending-the-model/ ) - doing this is very applicable to several of our use cases - does harness support model extensions? If not we request that it can be done. As an example we need to extend the model to add support for what we internally call canonical APIs which have properties that need to be required that are beyond what the normal API model supports.

Please help us to enable centralised notifications to monitor pipeline status and get notifications on Teams.

In the triggers of the harness pipeline, when we create a trigger for PULL REQUEST, there is only single ACTION, whether the PR is Closed or Merged. The name of that Action is CLOSE. So the issue is, whenever we Close or Merge the PR, both the time pipeline is triggered. Now we need the seperate Actions for both. One should be for Closing the PR and another for Merging the PR. So that, we can skip the builds of Closing the PR.

Enhance the execution filter by including additional details such as the project and PR number. When a pipeline name is selected, automatically display the stage dropdown and allow filtering by various states. Group all reruns under a single execution instead of listing them separately.

When use harness CET, we found a problem that the exception missing detailMessage of “view field content”. For example: When in OverOps: We can see from three dots “view field content”, this give us detail message to trace issue. But when in harness CET: I can’t find this 3 dots, can’t see detail:

When in OverOps, we can add this Notes column to dashboard to add Jira tickets ID or notes for developer team followup, but in harness CET can’t find a notes column. Please have a column to add notes in Harness CET or similar function.