incorrect order of statuses

[Edward Chun]

On my story board page, I have ordered my statuses

1. To do
2. In Grooming
3. Ready for Dev
4. In Dev
5. In QA
6. PM Signoff
7. Merged
8. Done

But for some reason when I open a story, the statuses are no longer in that order. Now it's showing

1. To do
2. In Dev
3. In Grooming
4. In QA
5. Merged
6. PM Signoff
7. Ready for Dev
8. Done

Does anyone know why this would happen? 

[David Leal · Accepted solution]

The name of the columns have nothing to do with the status, you can have a column that is tied to more than one status. You can put an arbitrary name. From the status drop down menu you will see only the valid next status according to possible transition from the workflow the issue has to obey. The order probably for this view will be alphabetical order group by the same status type (blue, green).

[Josh Carolan]

While you are correct for 'classic' projects, this post was tagged with next-gen, and actually for next-gen projects, columns map 1-1 with status'.

You are right though that the order of the status' in the drop down aren't ordered the same way as the board, they are just alphabetical within their status categories. This may be because as you said in classic projects, the status could map to different columns in the board and therefore, there may not be a logical ordering. 

[Edward Chun]

Thanks for the responses, David + Joshua. Is there a way to prevent the statuses from being ordered alphabetically in new gen jira projects?

[Josh Carolan]

Unfortunately not at the moment but you could raise a feature request at https://jira.atlassian.com/browse/JSWCLOUD-17648?jql=project%20%3D%20%22JIRA%20Software%20Cloud%22%20AND%20type%20%3D%20Suggestion%20AND%20statusCategory%20!%3D%20Done%20ORDER%20BY%20Updated

[Daniel Armyr]

+1 from me here.

[Daniel Armyr]

Go in and vote here for this feature: https://jira.atlassian.com/browse/JSWCLOUD-18903