Feature Requests

I would like to use DCM automation to add certificates to AWS Certificate manager. We use Harness and Terraform to deploy applications to AWS. I would like to automate the creation and renewal of certificates so that we don't have a production outage when certificates expire and reduce manual intervention.

Description: Currently, dashboard fields only render as plain text. When we concatenate pipeline execution URLs, the result is a string that users must copy and paste into a browser. Even attempts to format with HTML (e.g., <a href="...">) only show text, not a clickable link. Example Use Case: We want to create a field like “Open Pipeline” in a dashboard that directly links to the Harness execution. Today we can build the correct URL with concat(), but it’s not clickable. Why This Matters: Improves usability: users can quickly navigate from dashboards to pipeline executions without copy/paste. Saves time for operations and monitoring teams. Aligns with common BI/dashboard practices where links can be embedded for faster access. Requested Enhancement: Enable dashboards to render concatenated fields as clickable hyperlinks (similar to how Looker and other BI tools handle link formatting).

Currently we cannot show the day of the date on the harness dashboard . It shows data by dates only. It would be good if we can show both day of the week and the date.

Description: Currently, when users add a custom dimension to a Harness dashboard—for example, a pipeline execution URL—the value is rendered as plain text, even if the custom dimension represents a valid URL. As a result, users are unable to directly click on the value to navigate to the relevant page. Instead, they must manually copy the text and paste it into a new tab to open the link. This creates an unnecessary usability barrier, especially in use cases where teams want to track and quickly access execution details directly from the dashboard. Requested Enhancement: Enable support for rendering custom dimensions as clickable hyperlinks in dashboard tables or widgets when the custom dimension contains a valid URL.

We need to enhance the dashboard to display the following test-related information: Unit Tests – Count of test cases. If absent, display 0. Component Tests – Count of test cases. If absent, display 0. Contract Tests – Count of test cases. If absent, display 0. Integration Tests – Count of test cases. If absent, display 0. End-to-End (E2E) Tests – Count of test cases. If absent, display 0. Test Coverage – Overall coverage percentage (line or branch coverage; specify which). Trend Indicators – Week-over-week change for test counts and coverage. Impact: This will enable users to monitor test quality and progress over time directly within Harness, without relying on external tools.

We would like the ability to analyse and gather data for Harness Dashboards for > 6 months. currently, this appears to be the cut off.

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

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

For the tag values in dashboard the tag values don't update when in the folder. This means you can filter by tags that don't exist in a folder. This isn't a great experience for end users