You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
I have 2 filters
1) My Open Tasks
status not in (Closed) AND assignee in (currentUser()) ORDER BY priority DESC
2) My Open Tasks + Unassigned
status not in (Closed) AND assignee in (currentUser(), EMPTY) ORDER BY priority DESC
The first sorts by priority as expected. The second does not. I can't determine what it's sorted by but it's not priority. There are issues with priority of Highest in the middle of the list of results and Medium issues at the top. There are also "unassigned" issues before and after the Highest priority issues so it's not sorted by assignee either, which is the only difference between the two queries.
Am I missing something here or is this a bug?
Hi @bver
Maybe try:
status not in (Closed) AND (assignee = currentUser() or assignee is not EMPTY) ORDER BY priority DESC
No dice. Order changed a bit but still same overall problem. Still several Medium priority tasks above the Highest ones.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, it should have said IS Empty. You can try that again.
status not in (Closed) AND (assignee = currentUser() or assignee is EMPTY) ORDER BY priority DESC
I wonder if it has something to do with the empty as related to assignee. You might try just this to see:
status not in (Closed) or assignee is EMPTY ORDER BY priority DESC
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Neither work sadly. But I did comment here in the main thread as to how it is actually ordering / grouping the results. Maybe that will give some insight?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah it seems ordered by Project first, then Priority despite that not being part of the criteria. The first query did not return results from all projects so the Highest priority ones from one of the projects just ended up at the top.
So how do I force it to not order by Project first?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.