When using a multi-service stage (services.values) in a Native Helm deployment, Harness automatically names each service execution using its array index (e.g., Workload Plane Deployments_0, Workload Plane Deployments_1). There is currently no supported way to override these display names per service entry.

Customers expect to see meaningful names (e.g., Workload Plane Deployments_Frontend, Workload Plane Deployments_Compute) in the execution view, particularly when managing multiple Helm services within the same stage.

Current behavior:

Services in services.values are labeled using their index position (_0, _1, etc.) in the pipeline execution UI.

Expected behavior:

Users should be able to define a name field per service entry in services.values that controls the display name shown in the execution view, without breaking serviceInputs or being stripped by the visual editor.

Workaround:

Splitting into separate stages per service achieves the naming goal but increases pipeline complexity and is not a scalable solution for teams managing many services.

Customer impact:

Affects operational visibility and execution tracking, especially for teams running multi-service Helm deployments in a single stage. The current behavior has also led to confusion when AI-assisted suggestions recommend adding a name field that the platform doesn't fully support in this context.