Sorting jobs in workflows would make things so much easier! It reminds me of how organized guides on pixelflow help gamers navigate levels smoothly. Great suggestion for improving workflow clarity!

In most CI/CD systems (especially GitHub Actions), Veck IO you cannot manually sort jobs in the Workflows UI. Job order in the UI is determined by execution logic, not by visual preference.

Please add ability to _visually_ sort and group jobs.

I'd like to emphasise, this is not about the order of execution. This is purely about providing a nice UI. The current visualization is a mess, and it is really frustrating - to the extent that we a considering alternative services now.

+1

Went in expecting circleci to follow the order defined in the config.yml but nope.

Would be nice if we could define a custom order for better visibility.

This would be addressed by the request but, to add a little more granular context, it would also be helpful to have matrix jobs grouped

Highly needed, we have 40+ jobs 10+ workflows, finding basic build run is a challenge.

Sorry to say but I really feel your products don't know what features are most important to your clients, those small feature are very straightforward even from common sense, and can greatly bring in more clients to your company, another feature missing is be able to update parameters at run time on the UI so that we can dynamically change the value of some parameters, I am surprised those must have features in any CI tool is still missing here.

Hi all, thanks for your feedback and input here. Earlier this week, we shipped an update to the workflows graph on the new UI. The graph has been condensed, and hovering your mouse over a job will highlight lines to upstream jobs as well as downstream jobs that depend on it. While it doesn't directly address this request, we hope the above changes will help make your workflow graphs more readable per some of the other comments here.At this time, implementing any job ordering in the workflows graph is not prioritized by our product team. The post will remain open for votes and we can revisit in the future.

An ordered keyword at the top level with defined and dependencies options, where defined is yaml order and dependencies is run order would do it.