Feature Requests

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

As of now if we have cost preferences have setup we cannot see anomalies in perspectives. The request is to ensure that the cost preferences set for an account are taken into account during the anomaly detection process, providing more accurate and aligned results with user-defined settings.

In veracode scan or Sonar scan, once the scan is completed the result is available in the output in different severity levels eg: high, low, etc Similar to that feature, as a pipeline developer, I want to enable the test intelligence result output to be available in the execution output so that I can refer the facts not limited to - how many test cases executed? how many failed? what are test names? etc Benefits: Based on the output results placeholders, we can design the granularity to implement the quality gate or have a policy implmented.

We'd like the ability to add notes to our pipeline executions and have them show up in the pipeline execution history page. Currently Harness supports adding notes during the pipeline execution but the Execution History Page does not display these notes. We'd like for users to be able to see the notes and even filter based on the notes left as well.

Currently the only results you will see for STO in the security results page will be for the latest execution of the pipeline. That execution may not be the complete pipeline. In the case where the user has had a failure and resumes the execution from last successful stage, any scan results from that previous execution will not be displayed in the security tests page. User will need to iterate through the execution history to find the various scan results.

Allow a recommendation to remain as listed once it has been put into a new "In Progress Status". This gives the engineer a chance to return to the tool to register the action taken and provide a fair estimation of the actual savings gained. Sometimes it takes a few weeks before the savings can be seen in enough data to prove the value of the actioned recommendation. A5t the moment the Engineer only has until the next update, when the recommendation may just disappear! Mad!

Add the functionality in "External Tickets" ( https://developer.harness.io/docs/security-testing-orchestration/jira-integrations/ ) to automatically create a Jira ticket when an exemption is raised.