Feature Requests

The pipeline studio should show what the required resources are to run this pipeline. Why: We need an easy way to determine the required resources so we can properly plan, so that we can optimize the number of builds we can run per node.

Module download stats not present in Harness IaCM Module registry

Currently only for pipeline entities, gitconfig is available for policy evaluation. The feature request is to make this available for all entities backed by git manifest. This will allow use cases such as "disabling direct commits to main branch" or allowing pushes only on feature or release branches.

Developers many times reject the manual approval without any reason. We want to know why developers decided no for manual approval. This information is crucial for us to know why the pipeline failed. If we know the reason, then we can try to automate and make sure there is no need for manual approval.

If there are multiple user groups and I require approval for each of them, there should some option like this. Right now I do not find any approach for this

As an end user of Harness CCM I want to easily click a table row item in a visualisation to filter the dashboard, so I can reduce the noise and more easily gain reporting insights. When using the click to filter function in the BI Dashboards in Harness CCM, the filtering applies to all visualisations except the one in which the row was clicked. I have to go to a second table to click the same item to make the original table (visualisation) have the same filtering. I would like my end users to be able to click the item and have all of the visualisations in the dashboard respond INCLUDING the table where the filtering was originated.

Allowing only specific versions of services to deploy on Prod/Cob pipelines. This would help us to control deployments on production. Something that could help us mark specific versions eligible for deployment on Prod/Cob.

Currently we only get notification that workspace is drifted, but it would help us to know more details like its in drifted state from last 1 week/1 month/ 1year. Add-on details like what exact drift will be even useful.

Currently notifications setting are pipeline level, in cases where multiple workspaces share a common pipeline, need to send notifications to workspace specific settings. So notifications settings should be supported on workspace level, which should override pipeline level settings

For any given Harness instance we would like to see the status of Feature Flags affecting that account in a Harness UI, so we don't have to rely on Customer Support to tell us the status of feature flags which impact the way the Harness platform operates.