Feature Requests

Currently we are working with Xcode 16.2 and Swift 6 which generates some errors with SonaQube since the version available in Harness is Xcode 16.1. There is also an instruction from Apple to update to Xcode26 for the first months of next year. https://developer.apple.com/app-store/submitting/

Currently, there is no way to view all feature flags, their status, activity, etc across projects. The rollout board and environments tab can show feature flags for that project, but leadership would like visibility across all apps for a more birds-eye view of feature flag utilization. This would be useful to integrate into the Harness reporting capabilities.

Right now the rollback steps can only run on certain types of non-successes (namely Failures and I believe Expiries), which leaves some potential issues unkept/unattended when pipelines are aborted or otherwise. Ideally, we want to be able to optionally perform some kinds of rollback steps on any type of status of the pipeline other than success.

Currently, the Shell Script step does not automatically inherit or use permissions associated with a configured connector. Users must manually handle authentication, for example by writing scripts to assume roles when using OIDC. Problem Statement: This creates additional overhead and inconsistency compared to other steps that already leverage connector credentials natively. Users expect the Shell Script step to seamlessly use the same connector permissions without needing to manually replicate the authentication logic. Requested Feature: Enable the Shell Script step to optionally use connector credentials automatically (similar to how other steps handle authentication). This could be implemented via a toggle or configuration field that allows users to select an existing connector for credential context. Example Use Case: A user wants to run a script in an AWS environment using OIDC. Today, they must add logic in the script to assume the IAM role manually. With this feature, the step would automatically inherit the connector’s OIDC permissions, eliminating that extra scripting.

We would like to be able to update the next sequence id for a pipeline. We use the sequence id to version artifacts i.e. 1.0.0-<+pipeline.sequenceId>. Artifact version collisions will happen when migrating from jenkins, deleting and recreating a pipeline, moving a pipeline to another project.

PR_CHECK Pipeline webhook execution git lable change Need your availiability.

Please add support for specifying a CloudFormation StackPolicyBody when creating or updating stacks via Harness. This would allow us to apply stack policies that prevent accidental replacement or deletion of critical resources (such as DynamoDB tables) during updates, providing an important safeguard for infrastructure managed through Harness pipelines.

Been working on dashboards a lot in the last few months. Below are some ideas that I think would help make them more useful to users and creators. • Track Audit Trail for edits made to dashboard widgets. • Track Audit Trail for deletions of dashboard widgets. • Separate dashboard permissions for Create, Edit, and Delete actions so they can be managed individually. • Add metrics for IAC and FME. • Make Pipeline Execution IDs from "Execution History" accessible during widget creation. • Enable retrieval of a stage’s approval timeout value. • Create a measure or dimension that excludes approval wait time steps and their values from pipeline execution duration. • Allow linking of "Build and Repositories" data with "Deployments and Services V2" data. • Make "Unified View" and "Pipelines" Explore section/category data accessible in the "Continuous Delivery & GitOps" Explore section/category.

As a user, want to be able to select "All Environments" option in the deploy stage inputs, just like "All Infrastructures" while executing the pipeline.

As a user while executing a pipeline with depIoyment stage , I want an option to select "All Environments" similar to "All Infrastructures", so that I dont have to waste time inidividually selecting all environments.