Feature Requests

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

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.

HCSC requesting to have the ability to do validation on harness idp form itself, for example to check if the date selected is future/current datetime and is atleast15 mins after the current. and also have dynamic description on the ui:help

I want the flexibility to resume my failed IDP workflow from its last failed state, instead of restarting from scratch again. I can do this with a specific harness pipeline but not with an IDP workflow. In our case, we have workflow with multiple pipelines and failed workflows require lot of repeated runs. Ability to resume from last failed state will help a lot.

Summary SGWS wants to complete the approval for an IDP workflow-triggered pipeline from within the IDP workflow itself, without navigating to the pipeline. Current behavior A user runs an IDP workflow, which triggers a Harness pipeline. The approval step is defined at the pipeline level. The approver must leave the workflow and open the pipeline execution to approve. Requested behavior Either of the following, in order of preference: Approve directly in the IDP workflow view, next to the logs and run status. Approve by replying to an email notification. Business impact Users run everything from the workflow and don’t have access to the DevSecOps project scope where the pipelines live. Forcing approvers into the pipeline UI breaks the self-service flow.

Request Harness should support manual steps that wait for a user to sign off, so a full process can be built out in Harness before every step is automated. Background braintree/runbook has been used to automate large deployment processes incrementally. Runbook is a DSL for defining a procedure as an ordered set of steps, where manual and automated steps live in the same document. With it, all steps were put in place, documented, and partially automated, then automated in pieces until the process was complete. Core need A tool like this should not require 100% automation to be useful. Even at a fraction of full automation, having the non-automated steps documented in one place with correct dependency ordering helps with: Standing up new environments, where the full sequence (manual and automated) is visible and ordered Incrementally automating the manual steps, since each one is already defined and sequenced and can be replaced over time Example flow Define the full process in Harness, with every step in order. Steps that can be automated today run automatically. Remaining steps pause and wait for a person to complete the work and sign off. Over time, replace each manual step with an automated one. Gap Manual Approval works as an approve/reject gate rather than a documented unit of work. What it and other existing steps cover today should be confirmed. Suggested scope Markdown instructions per step Assignee or group, with notifications Sign-off audit trail (who, when, optional comment) Works with existing stage ordering and conditions Optional timeout Outputs that downstream steps can use Ability to swap a manual step for an automated one without restructuring the pipeline

Please enable the IDP_2_0 feature flag for account nPYQjrqZTXaBlyk50fEBoA and verify IDP is provisioned for the account. IDP is missing from the module switcher; /ng/account/nPYQjrqZTXaBlyk50fEBoA/module/idp redirects to a blank trial page, and the IDP frontend assets fail to load.

Problem Statement Our API Platform and API Governance teams are leveraging Harness IDP as the strategic enterprise developer portal for API discovery, cataloging, governance, and self-service developer enablement. While Harness IDP provides strong catalog capabilities, it currently lacks support for two key GraphQL ecosystem plugins commonly available in Backstage: Apollo Explorer GraphQL Voyager These plugins are currently not enabled/supported within Harness IDP and require custom implementation or external tooling. This creates a fragmented developer experience and limits the ability of application teams to discover, understand, validate, and consume GraphQL APIs directly within the IDP experience.