How to reorder status transitions in the new issue view

[#1]

In the Jira Cloud new issue view, the dropdown for status transitions ordering logic is not impacted at all by the order of statuses in the status settings screen (Settings > Issues > Statuses).

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 (To Do, In Progress, Done);
• Within category order alphabetically by name of the status being transitioned to.

So, to change the transition order in the new issue view status dropdown, it is necessary to include the opsbar-sequence property in the workflow transition, lower values will appear first.

1. From your project, go to project settings, then workflows;
2. Select the workflow from the issue type you want to change and click on Edit under the Actions column;
   
3. From the diagram or text mode, select the transition that you want to reorder and click on Properties, it can also be used on Global Transitions;
   
4. In the transition properties screen, add the opsbar-sequence in the Property Key column, and the numerical value in the Property Value column and Add;
   
5. Go back to the workflow screen and publish your draft workflow after you make the change to all the transitions needed.
   

Example before editing the transition:

Example after editing the transition:

[Kalin U]

Thank you for the official article on this. It might be useful to get it in the Jira Software Knowledge Base, so that fellow users find it there too.

Previously, I was able to find information on how to re-order statuses in these 3 places:

• an undated blog post by a UK service provider: The easy opsbar-sequence trick that simplifies complex workflows in Jira
• a 2018 community post: Opsbar question for JIRA cloud
• following the updates and the comments on the public tracker: opsbar-sequence property does not work in new issue view

[Pedro Henrique Fernandes]

Definitely worth of going to the knowledge base for Jira Cloud as a whole, I will take a look at that.

Thanks for your feedback and for the additional information Kalin. 

[Dave Mathijs]

Hi @Pedro Henrique Fernandes thanks for the explanation. I agree with @Kalin U that this should be elaborated in the documentation or KB as well. Bookmarking this topic for future reference.

[lex]

Thank you @Pedro Henrique Fernandes! This is super helpful and needs to be easier to find. There's a lot of outdated information out there that I found before coming across this.

[Phil Bustin]

I am finding that transitions from Any status do not follow the opsbar order.  I haven't been able to determine a pattern or how to work around it.

[Alicia Chung]

I've added an opsbar-sequence property to every status but am unable to override the default sort order (category + alphabetical). Each of the statuses has a global transition. Does anyone have any ideas?

[Grant Olson]

I'm having the same problem as Phil and Alicia mentioned above. Any help would be appreciated! Thank you!

[Phil Bustin]

Alicia, By "category" do you mean regular transition vs. Any-to-status transition?  And is the sort supposed to be by status or transition?  I have a status from which there are two "regular" transitions, to which I assigned opsbar sequences.  The appearance order is the worst possible one: the transition to which I assigned a lower opsbar sequence appears at the bottom of the transition list.  And, the alphabetical order of the two transitions as well as the two statuses is descending.

In the screenshot below, the "Request UT to MO Tasks" transition that appears at the top has a higher opsbar sequence value than the "Request BA Tasks" transition that appears near the bottom.  All the other transitions are from Any state.

Note that the two regular transitions are in descending alphabetical order, as are their target statuses.

It seems strange to me that we no longer have to way to control transition order, if that is the case.

[Alicia Chung]

Hey Phil, 

When I say "category" I mean the Jira categories ("To Do", "In Progress", and "Done") for the statuses: 

All of our statuses have a global transition, meaning that any status can transition into any other status. 

Regardless of which statuses I add the opsbar-sequence property to (all or just some), it doesn't reorder the statues in our issues view. You'll notice that "In Progress" comes after "Code Review" which is not the order we want. Same with "Done".

[Phil Bustin]

Opsbar Sequence is working for Any-to-status transitions, but no longer works for status-to-status transitions.  Also, the position for status-to-status transitions varies from status to status.  We have case PCS-268048 open with Support.

[M0214104]

@Phil Bustin any news there?

[Phil Bustin]

As I recall, except for one transition (the first?), all were in the correct order.  As I recall, I didn't pursue the matter diligently after I discovered that.  I'll try to look into it again.

[Sade Floyd]

I am having the same issue. Opsbar sequence is not working.

[Josh Martin]

Also having the same issue. Our transitions were reorganized last week (we didn't do anything... I assume something on Atlassian's side caused them to get reordered). Found this thread, tried adding opsbar-sequence to the transition properties and it didn't change anything. What is strange is that our transitions are not following the ordering rules that Atlassian has set... It's a mixture of status categories so we have "Done" statuses in the middle of "In Progress" statuses. Very odd....