Feature Requests

Currently no notification is sent to notify of a Scheduled Pipeline failing to trigger. A notification or email should be sent to notify the user/admin that this has occurred so that it can be addressed.

I often initiate builds that can take up to an hour and rely on notifications to know when they finish, allowing me to proceed with subsequent tasks. Instead of removing in-app notifications entirely, it would be beneficial to have more configuration options to control when and how they appear. This would enhance the user experience by providing flexibility in managing notifications according to individual preferences.

Description: Currently, the CircleCI Slack app only supports notifications for the default branch of a project. Teams frequently need visibility across more than one branch — for example, monitoring both main and a release branch, or a set of long-running feature branches. What we'd like: The ability to specify multiple branches (not just the default branch) when configuring Slack notifications at the project level in the CircleCI Slack app. Why it matters: Teams often have more than one branch that matters for operational visibility. Limiting notifications to a single default branch means teams either miss important failures on other key branches, or have to fall back to the Slack Orb with manual YAML configuration — which defeats the purpose of the no-config Slack app integration. Proposed solution: Allow users to enter one or more branch names (or branch patterns) when setting up project-level Slack notifications in the app. This could be a multi-value input field or support for wildcard/regex patterns.

The IP ranges ( https://circleci.com/docs/2.0/ip-ranges/ ) feature currently only supports the Docker executor. This request represents adding support for similar functionality on jobs that use the Machine executor.

Originally asked here: https://discuss.circleci.com/t/auto-cancel-builds-on-default-branch/5536 We would like auto-cancel to apply to the default branch, specifically because we have a deploy action associated with it. The deploy is slow and multiple builds are often racing with each other and we occasionally get an older build that finishes after a newer one, leaving us with older code deployed. (This is only for a staging environment deploy in our case though.) CCI-I-214

I would like to rotate our circle api token once a month with an automated process. I did not see such an endpoint. It would be useful to integrate this token into our other key rotation workflows. https://circleci.com/docs/2.0/managing-api-tokens/ This also relates to ticket CCI-I-482 CCI-I-628

Would like to see personal Slack notifications for user that triggered the workflow and just send to that person the notifications CCI-I-642

In some cases environment variables are useful to print out, it would be helpful to be able to whitelist the ones we'd like to show. CCI-I-1223

SARIF: https://sarifweb.azurewebsites.net/ Similar to how you expose test results in the UI/API, it would be great to support more generalized static analysis results. SARIF is a common format that can be used across many languages and tools Github supports SARIF format: https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github

Currently, we utilize holds on our workflows to require a pair of eyes to check on deployments heading to production. While a great feature, it is often unclear when jobs are stuck in a "hold" unless you're glued to the CircleCI console and are acutely aware that a build is being executed on a branch that even needs an approval. It would be very handy to receive notifications for workflows in a "hold" status, as well as to even approve them through Slack! CCI-I-1028