Feature Requests

When a third party has an error receiving the data sent to it from a job, or similar situations, it would be helpful to be able to re-run a successfully job from the UI. This is available in the VSCode extension and via API but would be helpful to have a quick button for it.

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.

Currently users are unable to filter for specific workflow types in the UI -- this can make searching for the status of scheduled workflows difficult, as users need to go back through completed builds to see the scheduled workflow in question. CCI-I-638

This helped me better identify the latest build when comparing to my app. CCI-I-1267

The new UI renders it very unclearly, especially when there are lots of jobs CCI-I-1273

You are able to see all workflows/jobs for a given branch by going to https://circleci.com/gh/{org}/{project}/tree/{branch} such as https://circleci.com/gh/socialtables/ent-killer/tree/master It would be extremely useful to see a list of all tagged jobs/workflows for all tags. We use tags to trigger staging/production builds and have no way of visualizing a record of all workflows/jobs of this type. Added filtering to be able to get workflows that have done a certain step would also be very useful. For us, viewing all workflows that have succeeded job deploy-production would allow us to fully use Circle to manage deploys. CCI-I-621

Currently it is possible to view jobs and workflows by branch but you can not specify further to show individual workflows. Users with multiple workflows may have trouble finding certain jobs that run less often when there may be many commits being made.An example would be a project (on any branch) with a workflow that runs per-commit and a secondary workflow that runs once per week. There would currently be no way to exclusively view the scheduled weekly workflow. CCI-I-757

It'd be useful to allow handling lists of values for a parameter, without having to resort to workarounds like parsing comma-separated lists in string types. I think it would be useful to be able to specify something like: steps: - myorb/foo: bar: - baz - qux And have the myorb/foo command called with a bar parameter equal to [ "baz", "qux" ] . CCI-I-701

Please strongly consider moving the cancel workflow element next to the workflow graph element in the preview pipeline details page, elsewhere or having some space for separation. Perhaps adding a confirmation to the cancel. This would go a long way to prevent accident cancels for pipelines and deploys.