Feature Requests

Widget to track status of epics and analyze work done, pending, distribution and estimation.

=> Lets create a template of type "Secrets Manager" having some "Template Inputs" => And this templates to create 'Custom Secrets Manager' connector , then the input variable value can be 'Fixed Value' or 'Expression' (of type "secret" only). => Here we have a requirement, where we want to use 'Expression' as a variable (it could be pipeline variable, stage variable or project level variable) => These variable values can be changed between 2 executions of same pipeline, without having to go back and change inputs in 'Custom Secrets Manager' connector.

After Harness introduced changes regarding Overrides, we have lost the ability to have runtime branch inputs on a manifest file for our referenced environments. When attempting to edit the override, the option to switch it to runtime input appears but after a save it reverts back to a normal preset input type.

In harness STO platform, we need a centralized view of exemptions raised across all the projects. Also, whenever there is an exemption raised, there should be an notification shown/sent.

Currently, only Pipelines, Steps, Stages, Feature Flags, Connectors, and Secrets can have naming conventions enforced. User wants this expanded to anything that can be named, such as Templates, Orgs, Projects, Approval Groups, Delegates, and User Groups. Currently there is no way to enforce naming conventions on these.

We would like to control environment name while saving the environment in project. Looks like currently Governance can be applied to the following Harness entities and events. Pipeline Feature Flag Connectors Template Custom https://developer.harness.io/docs/continuous-delivery/x-platform-cd-features/advanced/cd-governance/harness-governance-overview/#pipelines So we would like to check that the feature to invoke policy while saving the environment in the project is available or not. If not can you please let us know when can we expect this feature?

Requesting to enable PutSecretValue API as our internal organization is not authorized to use UpdateSecret.

The Governance policies set on repositories like protecting branches is available for each project, however there is no policy or way to enable the Goverance globally .

Currently, Jira creation from the pipeline is proxied through the delegate, while Jira creation from STO initiates directly from the server. In cases where this involves a protected Jira instance (e.g., passing through a firewall to an on-prem Jira), the STO call won’t be allowed unless firewall settings are adjusted.

Please make the emails of your recipients box in the notification section of a pipeline able to perform expression resolution. Pipeline -> notify -> new notification -> on failure -> email -> <+expression of user email based on who approved something in the pipeline> <+ pipeline.stages.Run _terraform.spec.execution.steps.HarnessApproval_1.output.approvalActivities[0]. user.email > This could be as easy as removing or changing a regex validation for the box.