Feature Requests

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.

(Austin Thao & Team) We need to make some improvements and recommendations for improving the efficiency of the pipeline that we have under experience—mcom. Harness Pipeline Trigger Options and Messaging: Can we deactivate unused build type options in code base (e.g., branch, git) for PR pipelines or at least add a description/message to clarify correct usage, and request a description field for CI code base. Harness Pipeline Step Re-execution Enhancement: In Harness can we have the ability to rerun individual steps (such as TSC, lint, or test) within a pipeline, rather than rerunning the entire pipeline, to improve efficiency. Harness Pipeline Status Update Issues: Harness to investigate why pipeline status updates (e.g., failed, pending, or blank) are not consistently reflected in Git and why some PRs are not picked up or updated in execution history. Thanks. Kannan

Add the ability for users to dynamically skip upcoming stages or steps in a currently running pipeline through the Harness UI/Template/Pipeline. This feature would provide greater flexibility during pipeline execution, allowing users to bypass certain stages when needed (such as skipping deployment stages during testing or maintenance scenarios) without having to stop and reconfigure the entire pipeline.

Currently, the Harness ServiceNow connector requires external wrappers or custom solutions for flexible table queries. We request native functionality within Harness that allows direct and flexible querying of ServiceNow tables without requiring additional wrapper libraries. This would simplify integration setup and reduce external dependencies while providing more robust ServiceNow data access capabilities.

At present tags from a Pipeline Template are not inherited by consuming Pipelines Would be nice to be able to selectively inherit specific tags so there when we have required tags in a Pipeline they can be pre-populated.

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=

Hi Team, We got a requirement to onboard users manually into project with email id. Ex., bharath.balasubramanian@transunion.com under one project. I need API to do the same. Can someone help at the earliest.

From a Harness customer: had an issue caused by Harness runners not having consistent usernames/home directories. Sometimes it's harness, sometimes its ubuntu. I had worked around a frustrating docker auth issue by hardcoding the path to /home/harness/docker/config.json, but that doesn't work anymore. The hardcoding is an issue on my side so I'm not opening a support ticket, just wanted to log that frustration

Core Functionality: Parse and display code coverage metrics from JUnit XML files alongside existing test results Coverage Metrics Display: Show overall coverage percentages with breakdowns by line, branch, method, and class coverage UI Customization Options: Toggle visibility of different coverage metrics Adjust threshold levels for pass/fail indicators Choose between different visualization formats Configure which coverage types display prominently Drill-Down Capabilities: Navigate to file-level or package-level coverage details for deeper analysis Backward Compatibility: Maintain full compatibility with current test execution display functionality Trend Analysis: Provide indicators showing coverage changes over time across different pipeline executions Integration: Seamlessly blend coverage data with existing execution history view without disrupting current workflows

When using package managers like apk and pip inside the container, these tools do not automatically respect the configured proxy environment. As a result, you see DNS resolution errors when attempting to fetch from your private registry. This is not a Harness issue, but rather due to how third-party tools like apk and pip must be explicitly configured to use proxy settings. Requesting that Harness create a feature/enhancement so that the apk, pip tools can go through the harness proxy settings to securely connect to the artifactory.