Feature Requests

Allow looping strategies like matrix, repeat and parallel when invoking a child pipeline as a stage inside a parent pipeline.

The minimum pollInterval is 2m (minutes), which is too long for certain CI/CD workflows. Creating this request to lower this poll interval timing for all artifact/manifest polling triggers

Please add the ability to use kustomize

When monitoring a pipeline in the console mode (which is our preference) It would be really useful if we could expand and collapse branches after they are complete. Similar to how the stage collapses when it is done We have some quite complex pipelines with nested templates to there is a lot of steps, which is fine when they are running but when they are complete they should roll up to a step group level (if there is one) (preferably by default) And allow us to expand and collapse at each point if we need to review. Also the left hand side should scroll to match the current execution section and finally - sometimes with multiple levels we get no info on the step, having a way to increase and decrease the size of the left hand side panel would be very useful Thanks

We need a overview dashboard to globally follow the usage of our template at Account scope in project pipelines.

Current Limitation: The Register Catalog step currently only supports IDP 1.0 ( backstage.io/v1alpha1 ) entities. When attempting to use IDP 2.0 ( harness.io/v1 ), the step fails because the Catalog API internally calls the convert API, which expects the older schema. Workaround: At present, users must replace the step with a Run step that directly calls the IDP 2.0 Create Entity API. This works functionally but bypasses the simplicity and governance benefits of the native pipeline step. Enhancement Request: Update the Register Catalog step to: Accept and process IDP 2.0 ( harness.io/v1 ) entities natively. Preserve backward compatibility with IDP 1.0 ( backstage.io/v1alpha1 ). Remove the need for scripting workarounds when working with IDP 2.0.

Would you please add the ability to use kustomize to deployments?

I'd like to be able to specify only a window start or only a window end in the ServiceNow approval step so that we can hold deployments until a specific start time, but allow them to complete any time afterwards.

We have set up user groups to receive notifications in the Microsoft Teams channel when approvals are required. However, it is currently not possible to approve requests directly within the Teams channel. Raising this feature request to enable approval actions via the Teams channel.

When taking a look at execution data, we want a method to filter out existing data from pipelines that have already been deleted. At this time, there is no method to do this, since the execution filters only look at execution data information and don't cross-reference against Pipeline data.