Feature Requests

Currently when a developer has a pipeline and it fails, its nearly impossible to do the calculation to see why the pipeline is failing due to over provision for resources. There should be a easy way before building to see how much cpu and memory that the pipeline is going to request. This will save the times where we see jobs not able to run and pods getting evicted for Harness SMP to run the build.

Currently we have audit logs being shipped to splunk. We need to alert when someone logs in local login. Currently we can't do that because audit logs do not explicit state with the login is via SSO or local login. Can harness add a Local Login action so we can then alert on this.

Email-based approval via reply rather than navigating to Harness UI to click approve button

Need Feature flags access for project NG-krchop-ngpp,promcp

We requires OPA policy enforcement on RBAC entity types - specifically Role, Resource Group, and Role Assignment — evaluated On Save. Additionally, the existing User Group On Save policy set is not being evaluated when a group is created or updated and needs to be fixed or enabled. The use case is enforcing guardrails for delegated project-level admins who have permissions to create user groups, roles, and resource groups, but must be prevented from granting admin-level access. Examples include blocking admin-named groups or roles, restricting Administrative Functions permissions to View-only in custom roles, and preventing binding of admin roles. RBAC alone cannot express these constraints since Role Create/Edit and Manage User Groups are all-or-nothing permissions. Please add OPA policy support for the missing entity types and fix evaluation for User and User Group policies.

In a Workflow form, a CustomField dropdown can only read other fields by their full path from the top of the form, such as targets[0].harness_environment. A dropdown inside an array row can't read a field in its own row. That means you can't have rows where one field's list depends on another field in the same row. Example Our onboarding form has one row per environment. Each row has an Environment picklist and a Resource group dropdown that should list only the groups that exist in that row's environment. What we found A dropdown in a row with dependsOn: [harness_environment] never loads and stays on dependencyNotMet. A dropdown in a row with a fixed URL loads fine. JSON Schema if/then, used to show a field once a row is added, is ignored. Request Let a dropdown in a row refer to fields in its own row, for example {{ item.harness_environment }} or targets[$index].harness_environment, in both dependsOn and apiOptions.path. Current workaround Each row's dropdown lists every environment and group pair

The Jira card in the IDP (Internal Developer Portal) Overview page directs users to Jira Cloud (Atlassian) rather than the customer's configured Jira On-Prem (Data Center) instance. The customer expects the card to fetch and display data from their Jira On-Prem environment with the same functionality available for Jira Cloud. Looking for onprem support.

We want to an ability to provide a different page link as the default and this should be at the account level, so any user who login will see this page instead of the default unified view. Right now we are using the user preferences setting but this requires update by every user and not a good user experience.

In IACM pipeline, output variables from a step are always passed as environment variables to later steps in the same stage, and a subset cannot be excluded (confirmed by Harness Support, ticket https://support.harness.io/hc/en-us/requests/132508 ). In IACM, the apply step publishes Terraform outputs as output variables. When one output is 128 KB or more, a later Run step fails to start with: fork/exec /usr/bin/sh: argument list too long The later step never uses that output. The apply succeeds, but the pipeline shows as Failed. So, The ask is a per-step setting to not inherit earlier steps' output variables as environment variables, or to inherit only an allow-list.

It would be great to be able to get CV data results through an api endpoint, both at service and pipeline level. Examples list of log groups/patterns marked as known for a service result of cv session (logs or metric) list of the new unknown logs discovered in an execution