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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,457,112
Community Members
 
Community Events
176
Community Groups

ORDER BY not doing anything at all for me.. using provided examples with standard fields

Edited

Assumption: setting ORDER BY will determine the order issues are rendered within columns

 

I've created the following quick filters:

duedate = empty order by created, priority asc

 (above copied from docs)

order by status
duedate = empty order by assignee

 

I've confirmed the `=` filters at least are doing something.. however no matter what I put for ORDER BY my board doesn't change in the slightest.

Is there something obvious I'm missing here?

 

UPDATE:

It seems the sort filter for the board trumps any sort filter you apply downstream

1 answer

2 votes

Hi @Cole Marsteller -- Welcome to the Atlassian Community!

Your assumption is incorrect.  Only the board filter's ORDER BY determines order on the board, even within the columns.  I believe the quick filters do not impact order.

Kind regards,
Bill

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events