Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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

Sort / Order by Status

Hi all,

When I sort by Status, the order is

  1. Parking Lot
  2. Delivery
  3. Discovery
  4. Ready for Delivery
  5. Done

I think that Delivery should appear after Ready for Delivery. Is there a way to fix that?


Similar request to this, to order by Now/Next/Later I've had to put a number in front of the title to order it properly

Hi @maxencetaieb There's no real concept of ordering for the Jira status unfortunately - it's a workflow and things don't have to be linear. If you want to do something like this I'd recommend creating a different field (a field of type "Select") to represent status if that's an option for you. However if you'd still prefer to use the Jira status field, know that you can still create a board where the columns are from that field - and you can reorder these columns to match how you want to see them.

@Chris Timms are you using a Select field for Now/Next/Later? If so that should work out of the box: - if that's not the case please let me know. 



Hey @Tanguy Crusson , I managed to test this today and can confirm, I am a liar :D the sort order works as you described.




Hahaha well maybe you came across a temporary bug, it's been known to happen 😅


Log in or Sign up to comment

Atlassian Community Events