Feature Requests

The UI provides a list of all the failing tests under the "Tests" tab, but they're not sorted. Sorting them (most likely by filename) would be super helpful when working on large upgrades with many failing tests while the work is in progress, so I can see which tests I've fixed and which tests I've broken between runs

Currently the config policy violation message only spans the length of the workflow status, name, and checkout source. It would improve readability to extend that across the whole workflow row

We can customize jobs and/or workflows based on pipeleine parameters BUT I cannot see none of those parameters in UI and cannot understand what particular job should do: compile? compile+deploy? compile+test? compile+test+deploy? deploy to instance #1? #2? #3? all of above? And add category "User Interface" to "Ideas" CCI-I-1616

Some times there are long parameter names for prepopulated parameters. This causes them to be cut off in the UI for the Run Pipeline modal. Adding a tool tip when hovering over a param name to display the full name would be ideal, but making the field bigger so that you can see the full name of the parameter would be good too

Similar to Github Actions: Creates an expandable group in the log. To create a group, use the group command and specify a title. Anything you print to the log between the group and endgroup commands is nested inside an expandable entry in the log. e.g.: echo "::group::{title}" ... echo "::endgroup::"

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

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.