Feature Requests

When re-running a workflow/job in a project with a large throughput and/or a large amount of users it can be very hard to find the re-run instance. There are many cases where a re-run of another user's workflow/job is being performed which makes it hard to filter for the re-run instance on the pipelines page. A toast with a link to the re-run would be helpful.

Description: Currently, CircleCI has removed skipped runs from the UI to create a cleaner experience. While this is generally helpful, there are cases where being able to see these skipped runs is valuable for troubleshooting and auditing purposes. Since these events are already recorded in the audit log, I'm requesting a feature that would allow organizations to optionally view these skipped runs in the UI. Use Cases: Debugging CI trigger patterns and configurations Verifying branch protection rules are working as expected Understanding organization workflow patterns holistically Auditing repository activity comprehensively Training new team members on CircleCI behavior Proposed Solutions Any of these options would address the need: A simple toggle in the Pipeline UI to show/hide skipped runs A repository-level setting in project configuration An organization-wide default that can be overridden per repository Business Value: This enhancement would maintain the current clean UI for most users while providing DevOps teams and administrators with the flexibility to see the complete history when needed. It would reduce the need to access audit logs for routine troubleshooting, saving time and improving workflow visibility.

Whenever some tests fail I have to go into the details of the tests job and click on "Rerun failed tests" in the button dropdown at the top right. I would love to have that button right in the pipeline overview when you expand a pipeline to reveal the workflow jobs. It would be amazing if there were a button similar to "Rerun workflow from failed" placed to the right of the job name, so I could rerun the failed tests without having to go into the details of the job.

We would like to define different pipelines for different triggers (e.g. on_push_master, on_pull_request, etc.) and define their configuration in their own .yml file. As far as I can see, there is no way to share local code (for example, setting up the environment) between those pipelines

While self-service audit capability by an end-user through the UI is a very nice feature, it would be great to allow for dynamic log shipping or making the audit logs queryable through the REST API , so they can be fed into a Security Incident and Event Management type solution. (or into Splunk, another logging tool, etc) As a fall out of the CircleCI Security incident announced in early January 2023 (rotate secrets), having the ability to quickly diagnose this data and compare it to other data we already had from other systems would have made security triage significantly faster/easier.

To retrieve test results in a particular time frame for a specific job, you need to step through a few endpoints and query job instance by job instance. It would be helpful if a job's test results were aggregated over a particular time frame, such as a month.

Desired State: users of CircleCI are able to identify how many jobs are currently running. Current State: users of CircleCI are not able to identify how many jobs are currently running and must email an account manager for this information. Impact: this prevents users from easily identifying the time period when jobs are being queued and prevents paid users from being able to verify if their jobs should be queued.

As per https://github.com/circleci/circleci-docs/issues/2040#issuecomment-368139737 It would be nice for users to have a way to shallow clone. Currently, we do checkout to checkout. It would be nice to be able to pass a depth into that like shallowClone:10 and then use the number 10 as the depth for the clone. The PR linked has a modified version of the existing script that works. CCI-I-254

Share your thoughts on our project administration v2 APIs. https://circleci.com/docs/api/v2/index.html New capabilities supporting webhooks, triggers, and configuration APIs will be available the week of April 8th 2025.

Currently, email notifications can be configured for either "All Builds in My Projects", "My Branches" or "None". It would be very useful to have an option to receive email notifications only for builds I'm the author of, i.e. "My Commits" rather than "My Branches".