Feature Requests

We want to be able to use github apps to centralise circle ci config for some of our deployments so its easy to propagate changes to the pipelines and avoid copy pasting the same pipeline in multiple repo's. However, we also want to restrict access to contexts such as our prod deploy context for this group of services but GitHub app based pipelines don't support this in their current state. The ability to restrict context access via security groups is a vital piece of the puzzle as we don't want ALL members of our GitHub org accessing these contexts

We want to reduce the number of API endpoints exposed to the public internet for security reasons. It would be beneficial if CircleCI machines could connect to our VPC using a private network connection, such as AWS PrivateLink, to access staging endpoints privately instead of over the public internet. Keywords: Ngrok, VPN

We often need to pause our scheduled pipelines temporarily for local maintenance operations that aren't merged into our IAC. Currently, disabling a scheduled pipeline is cumbersome, requiring multiple steps and the risk of forgetting to re-enable it. It would be very useful to have a dedicated setting to temporarily disable a scheduled pipeline until a specific timestamp, streamlining the process and reducing the risk of errors.

We need the ability to create scheduled triggers using a cron expression on a GitHub OAuth project without the GitHub App installed. This feature would enhance flexibility and compatibility with our existing setup, ensuring seamless integration and scheduling capabilities.

I want to know which tests are failing the most across all branches, not just master. It's nice that Insights shows the most failed test in each branch but 99% of the time what I care about is which tests are flaky when I submit a PR. CCI-I-785

At this time, the Insights API excludes workflows triggered by tag pushes. Adding this feature will allow customers to view workflows, including those triggered by tags via GET /insights/{project-slug}/workflows rather than having to query all pipelines. CCI-I-1413

A button on the releases dashboard to cancel an active release

Request to have the ability to set a workflow to trigger at the end of the pipeline. This could be used to:Perform a cleanup or teardown of resourcesEmulate sending webhook data (containing infromation about the pipeline)Trigger 3rd party integrations. CCI-I-1512

The Workflows results page (perhaps as well as other pages) could differentiate between passing and failing jobs more clearly as users with red/green colorblindness may have difficulty picking out a failed red job from a list of green ones. CCI-I-803

Ability to manage the security group membership for contexts via API: https://circleci.com/docs/contexts/#restrict-a-context-to-a-security-group-or-groups Currently this appears to be accessible only via the web UI.