Submit Your Ideas

We want to hear from you - vote for the features and improvements you'd most like to see, or submit your own ideas if you don't find them already listed.

Lock down ordering in workflow diagram

We have a pretty basic workflow process where we build a release, which can then be deployed on either a QA or a production environment. CircleCI creates the following diagram for it:

 

 
The diagram creation is a bit inconsistent: the order of the production and QA steps seems to be pretty random. Sometimes approve-production is shown first, and sometimes approve-qa. This makes it very easy accidentally click the wrong thing. Can the order be locked down so it never changes? Preferably to use the same order as used in config.yml ?
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Aug 24 2018
  • Future consideration
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    24 Aug 11:24

    See attached screenshot