Feature Requests

Re-creating branches in GitHub and then deleting them again is a terrible workaround and a big waste of valuable people's time. If you can't automate it, at least give us something to click in the CircleCI UI where we can delete branches, even if one by one. Just a simple page with the branch list and delete beside each one would seem to me to be super-easy. The ability to select a number of them and bulk delete would be even better. It just seems like such a simple thing that I don't understand not being there already. Thanks, Neil

Would be nice if the auto-cancel feature would be able to distinguish as different workflows in the same branch but with different incoming variables when using the API CCI-I-1419

I need better metrics to auto-scale machine runners effectively. Currently, our auto-scaling is time-based, and we need it to be on-demand based on queue times and other metrics.

I would like AI functionalities that can automatically detect flaky tests and track job performance over time. This would include identifying tests that fail intermittently and alerting users to address them.

I need CircleCI to have the capability to create or update Jira tickets directly from the pipeline, as this is crucial for our workflow automation.

Only GitHub Actions and GitLab are supported Trusted Publishers for NPM packages right now ( https://docs.npmjs.com/trusted-publishers#supported-cicd-providers ). With the rapidly upcoming changes to NPM ( https://github.blog/changelog/2025-09-29-strengthening-npm-security-important-changes-to-authentication-and-token-management/ ), CircleCI should become a Trusted Publisher.

I would like to have notifications directly into Slack or through email for intent data updates, as I primarily use the Chrome extension and do not frequently log into Cognizant.

I would like to have alerts sent to a Slack channel when a pipeline fails, indicating the specific policy failure and reason.

It would be great if budget control notifications could be sent directly to Slack, as this is our preferred communication channel.

Is there a way to indicate transitive dependencies in path filtering? For example, if a folder that has changed is used by another folder, which in turn is used by another folder, can we ensure full coverage of the change by testing downstream dependencies as well?