Feature Requests

Trying to output an error message to the Internal Developer Portal (IDP) execution view if pipeline fails. It shows the output message only if the pipeline succeeds but unable to do so for explicit pipeline failure.

The Confluence Search Plugin, previously available, has not been migrated to the new Backstage Backend system. As a result, teams are unable to access Confluence content directly within the IDP, impacting productivity and ease of access to documentation. Why It Matters: Accessing Confluence content seamlessly within Harness IDP is critical for enabling teams to find documentation quickly and efficiently. The lack of this feature has been highlighted as a pain point by several teams, who now need to leave the platform to search for resources externally. Request: Coordinate with the plugin owners to assess the feasibility of migrating the Confluence Search Plugin to the new Backstage Backend system. If external plugin owners cannot provide support, consider implementing an internal solution to restore this functionality based on team needs. Impact if Addressed: Improves developer productivity by centralizing access to Confluence documentation within Harness IDP. Enhances user experience by reducing the need to switch between tools, keeping workflows streamlined.

Summary: We’ve observed significant performance degradation in Harness.io dashboards when applying filters, particularly due to the large volume of data being queried. To address this, we propose an enhancement that introduces a feature flag to scope filter options based on user visibility—determined by their roles and assigned resource groups. Details & Justification: Improved User Experience Filtering large datasets currently results in slow dashboard performance, which negatively impacts usability and responsiveness. By limiting filter options to only relevant data, users can interact with dashboards more efficiently. Security and Compliance Alignment Presenting all filter options regardless of access may inadvertently expose metadata about resources users shouldn’t be aware of. Restricting filter visibility supports a least privilege model and aligns with internal security and compliance standards. Scalability and Future-Proofing As data volumes continue to grow, the current filter mechanism will become increasingly inefficient. Implementing scoped filters now will help ensure the dashboard experience remains performant and scalable. Suggested Implementation Approach A configurable feature flag could be introduced to enable scoped filters based on user roles and resource groups. This would allow organizations to opt-in without disrupting existing dashboard configurations.

We need a native Harness step to create a GitLab pull request (PR). This will replace our current manual workaround with shell scripts, making our CI/CD process more sustainable and scalable. Our existing process uses a dedicated action to create a GitLab PR, which is essential for triggering our security and compliance pipelines. To replicate this in Harness, we are currently forced to use a complex and hard-to-maintain workaround with shell commands and a custom Docker image. This manual process is not scalable. It makes it difficult to onboard new projects and introduces maintenance overhead, as any change requires updating many different scripts and templates.

Hi Team, The Harness-Vault connector is not capable of pulling keys from subfolders. It would be great if you could add this feature. We are adding subfolder details in the stage variable to fetch the keys.

Current CI stage status in Dashboards Build & Repo visualization We currently can’t filter by Stage Type or Status. Unified Pipeline visualization CI stage type is available, but we can’t filter for the RUNNING status. Request Could we add support for: Filtering by Stage Type and Status in Build & Repo visualization. Filtering by RUNNING status in Unified Pipeline visualization.

We'd like to remove the unused values in the values.yaml file in the BYOA GitOps Helm Chart. https://github.com/harness/gitops-helm-byoa/blob/8792d63df3845103f0db980e9df53b8f479633e0/charts/values.yaml#L399 For example, the values in global.image are not used anywhere here and just cause confusion for users.

Changes made directly in Github do not go through any validation. Harness only validates pipeline changes done through Harness UI. If we are to make a change to 300+ pipelines via Github, there is no way to run this validation right now. Request is to expose Harness validation API or build a feature where users can easily validate their feature branches.

When viewing exemptions at the account level, it would be helpful to have filters to view exemptions tool-wise. Additionally, having the option to filter by the requester would be an added advantage, as it would allow us to quickly fetch details for a specific tool raised by a particular person.

On release days, when everyone is trying to run merge their PRs, builds are waiting for a delegate(like this for 18m) and that is counted towards TIMEOUT value and stage fails with expired status. Which force developers to re-run and that results in more workload and wait time for everyone. So if you can provide a configuration option to exclude delegate wait time from TIMEOUT, that would help us. https://paypal.harness.io/ng/account/jLOlhyHHQ0yh8snNBDPL0A/module/ci/orgs/g_mobile_paypal/projects/um_iospaypalwallet/pipelines/iospaypalwalletfisci/executions/b1uXBrbDTPqC7zjSwPKG5Q/pipeline?stage=Jm7dTrfSRqmadLpvRUQ3Qg&stageExecId=Cp3jqpp2RvyFpBt0FDmk6g&step=TQjN6WBqRmabeFm-sCyurA&childStage=