Order by Rank ASC does not save

[robyn_graham]

Using ORDER BY Rank ASC, and once the filter is saved, when a browser refresh is done, it changes it back to ORDER BY created DESC, which prevents users from dragging/dropping tickets.

This is the actual query, even though I've tried to save it with Order by Rank ASC.   For the life of me, I can't get it to save it by Rank.   Very frustrated

status NOT IN (Published, "No Change", Canceled, "Ignored as Similar") AND created >= "2022-12-09" AND project = TROM ORDER BY created DESC

[Sam Okell]

Hi @robyn_graham 

If I remember rightly, the Rank is only available if 'activated' on the Project. If you add the Rank field to the screens of the work types you are using, then it should become available to order by.

Effectively, beforehand, you are trying to order by something that doesn't exist on the Project and so wouldn't work.

Try that and see how you get on!

[Daryl Marsh]

Change your filter to Project =TROM AND created >= "2022-12-09" AND status NOT IN (Published, "No Change", Canceled, "Ignored as Similar") ORDER BY RANK ASC. This should return the same results but does it more efficiently which sometimes changes the results. When creating a filter, I like to take the approach of filtering out the bigger items first. In your filter, you search on project last - meaning it looked at the status of all the work items, could be thousands or tens of thousands, in your environment first before moving on. Mine started with the project, which there is only one.

[John Funk]

Hi Robyn,

When you change it and then execute the query, does it look right? And then you do the Save Filter and Save Changes - correct? And there is no error message then? 

[David Nickell]

Alright -- I have to agree with John on this one as well... it is a bit quirky and I used to notice it more on changes to field layouts.   But make you change, execute your search, then save.   If you try to save without searching first, I think you can lose your filter changes.