Feature Requests

Description Today, in a pipeline execution that has multiple builds (e.g., re-runs under the same execution ID), the Supply Chain tab is only populated for the first build where SCS steps pass. For later builds in the same execution, even when SCS steps succeed, the Supply Chain tab is either empty or not populated. Why this is a problem Users (devs, leads, managers) often open the latest run or a specific build and expect to see Supply Chain data there. When the tab is empty for later builds, it looks like the scan didn’t run or the feature is broken. This makes it confusing to use the Supply Chain tab as a reliable view of each scan run. Requested enhancement Make the Supply Chain tab available and populated for every build in an execution where SCS steps pass, not only the first successful build. Each build view should show the Supply Chain info corresponding to that specific SCS scan run. This would make Supply Chain views much more intuitive in real-world pipelines where re-runs and multiple builds per execution are common.

I have created a step in harness as Harness Approval. and once rejected, I am getting message as below Sending notification to user groups for harness approval Request to REJECT this approval received by someemail@company.com with comments:{} and inputs:[] Can we change this text message as Rejected ?, as REJECT and approval received in one sentence is a bit confusing

We want the SSH connector with Kerberos connectivity to provide an option that would allow injection of the Kerberos token at the time of execution from JPMC specific token provisioning service so we can deploy on-prem with VSI We want the keytab to be treated as a custom secret manager to fetch a Kerberos token so it can be injected at runtime by calling JPMC specific kerberos provisioning service

waituntilhealthy doesnt work for argo rollouts, as argo rollouts start and go into suspended state for validation to happen. For argo rollouts consider suspended as a healthy state.

I need recommendation csv report via email for below email ids SureshKumar_Thanabal@newyorklife.com Vimala_sethuraman@newyorklife.com

Add filters to the overview page so it can be used by many, rather than just an all company overview. similar to the filtering on all perspectives

Currently, when a user creates a custom perspective and doesn’t complete the setup, the perspective still gets saved in the list. These incomplete perspectives appear with an orange box and an exclamation mark, which leads to unnecessary bloat and confusion for users trying to identify valid perspectives. Ask: Don’t allow unfinished or incomplete perspectives to be saved. Only save a perspective once the setup is successfully completed.

Reporting and monitoring of User engagement is an essential part of culture change in an organisation. The Audit trail is the only record we have of end users logging in and creating or editing Perspectives and Dashboards. Please enhance the trail by: Allowing "exclude" in filters Enable Column sorting Provide export to CSV capability Recognising automation activity as a User type Allowing Scheduled reports Allow more than 1 record type in a filter, eg perspectives and Dashboards Allow the choice to report distinct Users as opposed to distinct transactions OR Bring the data into the BI Dashboards as a tile type

Allow for drill down filtering in the line graph view when clicking the data point, similar to behavior when clicking the top of the bar graph view. This would make the behavior consistent, and allow for usage of that fast filtering feature without toggling back to the bar view.

In the Tests tab, is there functionality to view tests skipped by the test tool itself, and not Harness intelligence. So let's say in the command to run the function, someone sets a flag to ignore these specific suite of tests; is there a way for those skipped tests to be seen in the Tests tab? Thank you