Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

incorrect order of statuses

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

Screen Shot 2019-02-28 at 4.43.04 PM.png

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


Screen Shot 2019-02-28 at 4.47.35 PM.png


Does anyone know why this would happen? 

1 answer

1 accepted

0 votes
Answer accepted

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).

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. 

Like # people like this

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

Like # people like this

+1 from me here.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events