Feature Requests

Please consider a way to close the Dashboard Tags panel. It takes up valuable real estate especially when viewing on a laptop, ipad or tablet

Calculation fields in Dashboards are created per tile. It would be more efficient to at least be able to apply the field to any tile in the Dashboard. Beyond that to be able to apply the field to another Dashboard in the folder by selection. Often many calculation fields are needed to produce a result and duplication of tiles and Dashboards is a limited work around

https://coles.harness.io/ng/account/bbkQE2KNQWSaVWO0c5pR1A/admin/overview Admin overview is not editable, and makes it not very useful as a landing page. Noting that a similar page in IDP is fully editable. Would like this raised as a feature so that the page can be personalised for our company, as the page already has welcome <username> it would be the perfect landing page if it was able to be modified.

Feature Requirement: Global Tag-Based Dashboard Filtering Objective: Implement a function that enables users to filter dashboards by tags across all folders, regardless of their current location in the folder hierarchy. This feature aims to help users locate dashboards that may have been misplaced or are difficult to find due to inconsistent folder organization. Functional Requirements: Global Tag Filter: Users should be able to select one or more tags. The system should return all dashboards associated with the selected tags, regardless of which folder they are stored in. Search Scope: The filter must search across all folders and subfolders within the dashboard repository. User Interface: Add a tag filter component to the dashboard search or navigation UI. Display results in a unified view with folder path metadata to help users identify the dashboard’s location. Tag Management: Ensure tags are consistently indexed and searchable. Consider implementing autocomplete or suggestions based on existing tags

Currently, BI Dashboard can be deleted using "Move to trash" option while in the dashboard screen and a popup shows "Only administrators can retrieve items from the trash." However as a Harness administrator, we cannot see the trash in UI and there is no API as well for us to view and recover deleted dashboards. We have raised a bug https://support.harness.io/hc/en-us/requests/88042 for this but accordingly this feature request is needed to enable BI Dashboard Trash in UI and allow Harness Admins to restore deleted dashboards.

The Looker Dashboards have a huge area at the top in which any global filters are placed. When placing a filter eg Cost Categories, is it necessary to have both the Cost Category filter and the cost bucket? This doubles the space used and puts useless items into the filters. When viewing on a laptop, the real estate is half the screen. This makes the rest of the Dashboards visualisations very hard to view. Scrolling down the Dashboard can also make a large panel of white appear at the bottom. Sometimes there are 3 levels of scroll bar in the Users view. There is a problem with the way Harness has embedded Looker, which is not allowing dynamic resizing in a good UX design way. Please review

It appears that the parameters by which Harness moves their Recommendations to "accepted" status is too rigid. It doesn't appear to be observing the ticket's resolution field, and is looking at the status, so anything outside of the actual "Done" status won't be accepted We'd like Harness to either allow us to customize the acceptance criteria, or broaden the range.

We would like the ability for our Annual reports to have the ability to set a budget alert based on the monthly budget numbers, and exceeding them beyond a certain level. Currently, the alert is only based on the Annual total cost being exceeded.

We would like a method to take recommendations that are made with CCM and move them into the ignore List via API or through UI. We'd like to mark wildcards and for it to be able to process it. For example, all machines starting with windows-*

When actioning a recommendation Engineers often find the recommendation too harsh or contravenes a SaaS requirement, but they are able to implement a partial action of the recommendation and estimate their own more appropriate amount for the Savings $$$ figure. The integrations with Jira and SNow need to allow for the setting of the new amount when closing the ticket, populating the recommendation in Harness with the new estimated savings amount. They do not do this currently