Feature Requests

Current Harness Delegate logs do not distinguish whether errors such as SocketTimeoutException, ConnectionRefused, or UnknownHostException are caused by internal failures or external services being down/unreachable. This makes it difficult to troubleshoot and classify issues in Splunk. Request: Enhance logging to include: Dependency name (e.g., artifactory, github, vault etc) Full endpoint or hostname used Structured error type (timeout, dns_failure, connection_refused, etc.) JSON‑structured log format for machine parsing Business Impact: Clearer logging will reduce troubleshooting time, enable reliable Splunk alerting, and help quickly identify outages of upstream dependencies. Acceptance Criteria: Dependency identified in all related log entries URL/hostname included Error type classified Logs emitted in structured format (JSON preferred)

Artifactory supports OIDC connections, having the ability for a user to utilize that would be useful and reduce manual scripting to generate a token from a curl call. In fact many of our plugins could benefit from a generalized OIDC connection option as their respective technologies adopt the option.

Project Admins/Owners must be able to add users to their own projects, but they should only be allowed to add users who belong to the same Org. Cross-org user assignment must be blocked. Current situation: We have removed “invite user” permissions from our org admins, but Project Admins/owners can still add any already-provisioned user from other Orgs that will bypass our IDP only based access for organization. Current harness RBAC alone does not support restricting assignments by Org. In our SMP instance we do not see any policy types related to Access Control or Role Assignment governance. Can you please advise: Whether Access Control / Identity Governance policies are supported in our SMP deployment If a feature flag or module needs to be enabled to allow policies on user/role assignments What options you recommend to technically enforce this requirement We are looking for any supported approach or new ideas to achieve this restriction.

The current email step only supports TO and CC fields. We request the addition of BCC functionality to enable confidential distribution list management.

The Terraform provider does not support creating Splunk connectors using HEC Tokens, even though this configuration is possible through the UI. Resource Link: https://registry.terraform.io/providers/harness/harness/latest/docs/resources/platform_connector_splunk

Ask AI chat should show up at all levels in harness. Currently the button vanishes inside executions, environments, services, etc...

We would like the ability to reference IACM Workspaces via tagging when creating Resource Groups. This will allow us to more effectively apply RBAC permissions and governance for workspaces between project within our Harness environment.

Users currently are locked into all templates defaulting to the .harness/ path . being able to edit this (.harness/Account, /harness/Org, etc) or to unique folders would enable clean user and template promotion workflows with much less clutter.

We would appreciate the ability to set email priority levels (High, Normal, Low) to better communicate urgency to recipients.

Hi Team, Client needs to replace pipeline name whichever service or job has been triggered at that time for ex: if PDB-job is trigger the pipeline name should be pdb-pipeline Thanks Sanketh