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.

Currently the "From email" exists on the SMTP setting which is generally at the account level Ref: https://developer.harness.io/docs/platform/notifications/add-smtp-configuration/#step-2-details . There are requests from internal customers to have this from email customizable. For instance, any setting at the Org/project level or the email/notification step level. It would help to have this feature and would be beneficial for the teams that operate at the Org/project level

Currently In the pipeline details page, the UI displays the Pipeline name directly from the YAML. However, when switching to Input Sets, the name is fetched from the metadata value stored in the database at the time of pipeline creation. Because of this, if the name is later updated in the YAML, the Input Sets view will still display the original metadata value.

In policy violations side-car page, search based on components/licenses defined in the violation rules

Severity of the policy set (warn or block) shown in the policy violations dashboard (Pipeline execution summary)

The name of the policy should also be shown in the Pipeline execution summary. This helps the team to identify which policy sets were violated

We need some way to tell when a pipeline was invoked directly or when it was invoked as a sub pipeline of another pipeline. This would allow us to condition some stages in the pipeline based on the source of the execution

We cannot tell if someone aborted the verification step when Abort Verification is used. https://developer.harness.io/docs/continuous-delivery/verify/configure-cv/abort-verification/ We cannot tell historically when looking at the pipeline. It only appears as a success or failure with a general "error"

We'd like to add secret/expression support when creating GitOps clusters. Currently, any of the authentication methods require the user to input passwords, tokens, certs, etc as plaintext. We'd like the ability to pull these from secrets instead.

When I update a pipeline stored in Git, the platform automatically sets up everything, including the PR, and then closes the modal. However, I would greatly appreciate the ability to view the newly created PRs immediately, rather than having to navigate to GitHub and conduct a search.