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

?

Option 3

I think Option 3 makes sense in the short term, but I agree with Mike Alexander that setting custom properties seems a bit hacky in today's day and age for the purposes of configuring such a fundamental part of the UX. I would imagine that at some point, a configuration UI would exist within the Workflow setup to be able to drag and drop the order.

Option 3 for use would be the best one. Would be fantastic if combined with drag&drop ordering. 

For us, option 3 is the best of the three.

A drag-and-drop ordering would definitely add value.

Another vote for option 3.

However, having to manually control the order by setting a numerical value in a custom field is antiquated and not something I'd expect from such a major software company in 2020. Have you considered allowing the order to be specified via some sort of drag and drop mechanism?

Option 3 would be great

Voting for option 3

Voting for 3

I really prefer the most consistent solution even if it takes longer to implement.

The 3rd option gets my vote 

Definitely Option 3 look to be the best. I can create a specific order without fudging transition titles or categories. Perfect!

Thank you for the opportunity to provide input.

Option 3 please.

Option 3 is IMO fair compromise for everybody. 

Just for me to be 100% sure - if there are 5 traditions with sequence and 2 without - those 2 will be "at the end" ordered by the category and tan a-z?

Hi everyone,

Matt here again from the Jira Cloud team. We have dug deep into this to understand how the opsbar-sequence property works and how we can bring this to the new issue view. We have a few options in how we can proceed and I wanted to understand which direction would work best for you and your organisation.

Before continuing let me clarify how the ordering works between the two issue views currently.

We are currently considering three options moving forward:

1. Don't change anything

I understand this won't be a popular option in this thread but I'm being open that this is an option we have to consider.

2. Adopt the ordering used in the old issue view in the new issue view

The benefit here is that opsbar-sequence would work and the ordering would be exactly the same between the new and old issue views. We are worried that this ordering is very convoluted and difficult to understand. To users this ordering will likely appear arbitrary when opsbar-sequence isn't used.

3. Create a new, more intuitive, ordering logic that will apply across the new and old issue view

The approach here would be to "tidy up" the sorting logic in the old issue view and then have the new issue view use the same logic. Our new logic could be: always show transitions with the opsbar-sequence property first, then show remaining transitions ordered first by category (Todo, In Progress, Done) then alphabetically by name. This would provide the best of both worlds where opsbar-sequence works and where it isn't used the ordering is intuitive. We worry that this change in ordering could be jarring for users in the old issue view, even though it's more intuitive it's still a change.

I welcome any and all feedback on the above options that we are considering. We are committed to giving you the power that you need to deliver a great experience to your users and want to work with you to get this right.

Kind regards,

Matt

Just adding another "this affects me" comment. We've just rolled out a new Jira-based support process for our Business Operations team and were shocked to find that we can't order the statuses in the drop-down, and that what appears to be the first report of this issue (https://jira.atlassian.com/browse/JSWCLOUD-13864]) was from over 4 years ago...with no resolution in sight.

I'm glad to have found this one and that it appears to be a priority to address. Looking forward to the fix.

Hi everyone,

My name is Matt, I'm a product manager on the Jira Cloud team. We hear you loud and clear and are currently scoping out a solution to add to our short-term road map.

I'll keep you informed as we progress with understanding this problem and working on the solution.

Kind regards,

Matt

Can we please get this fixed? When we have a new ticket the first option in the drop down is to close the ticket and people keep selecting it because it's first. Sure, it's a training issue but it's also human nature to want to just pick the first option in the drop down list to start the ticket.

Besides, this ticket is nearly two years old!! Billion dollar company - can't fix the order of a drop list. We collectively pay enough in licensing to get something this simple fixed.

Thank you.

I have opened a new service desk for Change Management process and the stakeholders want me to adjust the drop down behavior. I have made the correct changes but because of the new view they will not take affect. I really need this to work as the stakeholders are very animate about making this work. 

Please help us out by allowing use to be able to do this in the new view so we don't have to make very one move back to classic view. 

This bug is also present in Jira Server, we are on 8.5.3.

I wholeheartedly agree with all other comments.  Its silly this not being addressed.  It's such inconsistent behavior from a new issue to an issue that has progressed thru the workflow and the transition buttons are ordered as defined by the opsbar-sequence property.

I'm getting grief from my users, especially on a very high profile project used by management, that the order of buttons is confusing and should be corrected. ;-(

I agree this is a major bug in the new Issue View and needs to be addressed ASAP. It's ludicrous that the only workaround is to prefix status names with a number!

This is a major step backwards in usability for users of the new view. I agree with others that this is not "Low" - I'd call it "High" priority.

The new view should support all of the functionality of the old view if you want users to switch to it - this is a big gap in that respect. Numbering transition steps is not a reasonable workaround!

Can't believe this was ignored, in the transition to New Issue View. The path of "where to go next" is scrambled.

I agree with Mark, this might seem small to a software development company, but when you're running Jira in a mixed environment it's actually really important to be able to do this. Users ask me ALL THE TIME to change the order of the buttons because it's confusing and they do not understand that they can look at the workflow to see happy path - nor should they need to.

I diagree that this is a "Low Priority" bug.  Per the bug fix policy, it is a "High Priority" bug as "users [sic] job functions are impaired".  Low priority is defined as "smaller paper cuts such as cosmetic errors".  This is not a cosmetic error.  We have numerous users relying on the presentation of transitions to indicate what to do.  I'm very surprised that this was simply ignored in the design of the new view; no sane person who seriously is involved in hard-pressed users dealing with workflows could consider displaying transitions as they are currently in the new view as an "improvement" or the change as a "cosmetic error."

The only working workaround seems to be adding numbers to statusi (rather than transitions). 

I have experience in helping people to setup their first service desk in Jira Cloud, and many Jira server implementations. People have concept of right sequence of actions, such as "Done" before "Escalate" or "Cancel", also "Approve" before "Reject", etc. The sequence shall show to the users the most natural choice from top to down.   
So, a  Jira designer shall stay rather with the old issue view , if the process owner insists on the order

As noted on the duplicate issue, the order of transitions is very important, especially for new people: 

As a person new to this company/department/issue type I want to see transitions distinguishing between happy paths and exception routings so that I can route issues assigned to me without confusion.

Thanks Tim.  However I would say in many cases that workaround will not be a very desirable approach.  For non-linear workflows it will be confusing for a user to see what appear to be step numbers in the workflow selection.

In the new issue view, it is sufficient to put a sequence number before each of your transitions in their name. (e.g. first transition in your list has name '01. Created', second has name '02. Analysis Ongoing', ...). In this way, you have a workaround to order your transitions in the proper sequence.