Feature Requests

Currently there is no way to see the currently running operations except opening the "JOBS" page and scanning the list, however this does not show parallel jobs. It would be nice to see the currently running jobs/containers at the top of the page for example so you don't have to scroll and search for them. For example we had a job that was stuck for 10+ hours and it was already gone from the first pages so we had to check multiple pages to find it and terminate it. (This does not happen often, but still a good reason to be able to see running containers at a glance.) CCI-I-810

A single view that lists how many jobs are waiting due to lack of containers. Trying to find a concise way to see a report/stats on how long we spend waiting for compute resources. CCI-I-1613

Adding a link to the most recent deploy in github would be extremely helpful. I have CircleCI setup with a deploy step for PRs to now.sh , but no way of seeing the deployments URL within Github. CCI-I-416

Currently, when a user hits their concurrency limits there is no error message. They will see their builds queueing. The user can use the CircleCI v3 API to get unclaimed tasks for a given resource class( https://circleci.com/docs/runner-api/#get-api-v3-tasks ) to confirm that they have unclaimed tasks. At this time, user rely on CircleCI Support team to share a list of jobs that need to be cancelled. This feature request is for better error messaging when concurrency limits are hit and for exposure to which jobs need to be cancelled in order to move forward.

We’d like to see real-time concurrency usage directly in the UI. Right now, there’s no way to monitor active jobs, queue lengths, or how close we are to our concurrency limit—until we hit it. A live view showing current usage, limits, and queue times would help us better manage workflows and plan for scaling. This visibility is key for deciding when to optimize or upgrade, rather than reacting after delays occur.

In our organizations, we actively use parallels, especially during tests, and try to dynamically manage them depending on the priority of the pipelines. On the "Setting/Plan" page, we have information available that according to our plan, there is a limit of 80 cuncurrent jobs. And I'll tell you, from my feelings, we often reach this limit. It would be great if you could design a page that would contain statistical information for the entire account, with some minimal historical data of 1-3 months. Which would show threshold and actual usage in the form of a graph. Best regards, Leonid Prytuliak DevOps Engineer at Ablefy GmbH

Like most engineers, I prefer to use a dark UI. CCI-I-930

While CCI allows you to separate builds into steps, it's very common to find that a singular step is multi-phased itself. It would be extremely helpful if, within a build step, the output was timestamped. This is the Jenkins equivalent: https://wiki.jenkins.io/display/JENKINS/Timestamper I'd be most interested in the duration feature, more so that having the timestamps and needing to work out duration of steps myself. CCI-I-360

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.

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.