Is there a way to do this in the new view without having any transitions? Currently all status's are set to have the "Allow all statuses to transition to this one" permission set

Thank you, @Scott Fannen for sharing your silly mistake, I did exactly the same mistake and found a solution thanks to your messages

I'm seeing this to in Jira Cloud. After reading this issue, I swapped to the "old view" and it shows correctly. In the new view it doesn't.

Irritating!

(Ignore this - user error. Just in case anyone else made my VERY silly mistake, the opsbar-sequence goes in the transition not the status)

I have reordered the statuses but I am still encountering the issue:

Awesome.  Thank you Matthew!  I can confirm that it's working for us as expected.  I greatly appreciate this effort by Atlassian and am thoroughly impressed. 

Hi everyone,

The fix for this has now been rolled out to 100% of production users and every instance should now see the opsbar-sequence property honoured in transition ordering in the new issue view.

The approach we have taken will only affect the ordering of transitions within the new issue view. Nothing will change in the old issue view. The ordering logic is as follows:

• Always show transitions with the opsbar-sequence property first according to their opsbar-sequence value (lower values appear first)
• Then show remaining transitions ordered first by category (Todo, In Progress, Done)
• Within category order alphabetically by name of the status being transitioned to

Thank you all for your support and patience as we worked on this. Please don't be afraid to share any stories or workflow improvements that this allows so that I can feed them back to the team.

Kind regards,

Matt

Thanks a lot, Matthew 

Perfect timing as we're just in the process of reviewing tons of workflows and promoting the new issue view.

Hi everyone,

Matt here again, a PM on the Jira Cloud team. Thank you for your feedback and patience as we work to resolve this issue. I have some good news to share, we have implemented a fix and will be rolling this out at the beginning of next week.

The fix that we have implemented is similar to option 3 above. The approach we have taken will only affect the ordering of transitions within the new issue view. Nothing will change in the old issue view. The ordering logic is as follows:

• Always show transitions with the opsbar-sequence property first according to their opsbar-sequence value
• Then show remaining transitions ordered first by category (Todo, In Progress, Done)
• Within category order alphabetically by name

As we roll out we'll be closely monitoring feedback and this ticket for feedback. Again, thank you for your engagement and patience on this one.

Kind regards,

Matt

The longer I'm thinking of this, the more doubts I have. Option 3 is such an obvious option to pick - how could we even be asked whether "the new, more intuitive, ordering logic" should be considered? It sounds like an inevitable task.

The trap is - this new better logic may stay on the Roadmap for ages (the topic was started nearly 2 years ago). 

Maybe we should be asked instead:

Option 1. Don't change anything now, and LATER improve to better logic

Option 2. Adopt old ordering ASAP, and LATER improve to better logic

?

As far as the best end user UX goes, they usually expect the order to be in line with the order of operations that is visible when viewing the workflow. That being said there are a lot of complexities when you try and look at the diagram of the workflow and base the ordering off of that... Especially when you have global transitions mixed in... Where would those live...

So my vote would be for option 3. Maybe even give the project admins the power to change it. In server you have enhanced permissions for project admins and they can modify the basics of the workflow there. Just add the ordering there.

It would be nice to have the enhanced permissions for cloud as well. Next-gen projects are nice and all but they just do not work for large scale companies that need consistency across all of the projects in an ORG.

So MVP for me would be just bring the sequence number into the new view and have it take priority over the "new" method in the new issue view. Then work to provide a more intuitive interface that project admins can control own destiny.

You have to always come at it from "teach a person how to fish" rather then just catching the fish for them and handing it to them... Its more scalable. And to be honest... saves us admins from the grunt work...