nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to sub sort Jira filter based on Priority?

Jimmy Trivedi

I want to sort Jira issues based on Priority. Please note, that I'm already sorting based on resolved date, but let's say, I have 4 issues out if 100, with same resolved date with different priorities. So what I want is in that 4 issues, whover priority is High that should come first, then medium and then low.

Please note: Make sure, first resolved date order should maintain, and if resolved date are same, then it should maintain priority order.

As of now, I configured 3 priorities:
High, Medium, Low

Query for my Jira Filter:

project = GJP AND status = Done AND assignee in (currentUser()) ORDER BY resolved DESC, priority ASC

Thanks in advanced!

Accepted answers

Jimmy Trivedi

I solved using this answer: https://community.atlassian.com/t5/Jira-questions/Is-possible-ORDER-BY-two-fields-in-JQL-search/qaq-p/1313294

All comments

Ismael Jimoh

@Jimmy Trivedi

Adding a comma to your order by and stating priority will sort by priority. What you have to watch out for is that Jira applies each order by based on a turn by turn based. In your case it is:

Order by due date first
then order by updated
then order by rank

If you add Priority at the end then only after performing all other sorting does it perform priority sorting and if you add it first, it’ll first sort by priority and then only your other other by.

Have you considered using board swimlanes feature to further divide this whereby you can then have issues categorised by their priority? This only works if you are not already using the swimlanes for something else.

Jimmy Trivedi

Hi Ismael,

I'm not sure how to check "swimlenes" feture.

Also I tried this:

project = GJP AND status = Done AND assignee in (currentUser()) ORDER BY resolved DESC, priority ASC

And I configured priority like this:

High

Medium

Low

Ourput: For same resolved date: Low, High, Medium is coming, is should come High, Low, Medium

Note: Please check the edited question.

Nic Brough -Adaptavist-

Have a look at the order of your priorities in the admin -> issues -> priority screen, that should be controlling the ordering in the output when you use "order by priority"

Swimlanes are a board feature that slice a board into horizontal sections, defined by more filters (or some pre-set data items, like "by story"). In your case, I would be thinking to define swimlane 1 as "priority = high", then lane 2 as "priority = medium" and so-on

Jimmy Trivedi

Hi Nic,

So, my requirement is to use Jira filters only, due for some specific reasons. Also, I want to inform you that I have some other filters and that are working fine according to my requirements, but this particular resolved filter is not working.

So, In that filters, I did one testing.

Scenario:

I created 3 issues with today's due date with 3 different priorities, High, Medium, and Low. So all 3 are showing on the first 3 rows because of the due date, that's fine. But the priority order is not coming properly. It should come High, Medium, Low due to ASC order, but it is coming in random order. Why?

Nic Brough -Adaptavist-

Gahh, hang on, I've completely missed the point here.

One of your searches is working ok accidentally.

Your searches include "sort by resolution date" which is being shown in the results as a date, but actually, the field is a date and time field. So your list that shows three on the same date resolved in order low, high, medium is showing them that way because of the times they were resolved on the day!

Jimmy Trivedi

Hi Nic,

Got it, I also thought once that this could happen, but there was no time mention, so!

Also, need one more clarity. What about my other filter? Please check the query, there also order is unusal.

Query:

assignee in (currentUser()) AND project = GJP AND status in ("In Review", Pending, Reopened, TODO, "Work in progress") ORDER BY due ASC, priority ASC

Ismael Jimoh

@Jimmy Trivedi

Despite the fields appearing as simple dates in your filter, they are in reality date time fields. A simple hover over the created date will show you the full stored data.

Can you instead use resolutiondate instead for example:

order by resolutiondate DESC

This is a date only field whereas your resolved is a date time field.

So long as one is resolved at a time after the other, you will get the result you described.

Regards.

Nic Brough -Adaptavist-

Sorry, no, that's wrong. Resolved is an alias for resolutiondate and resolutiondate is a date and time, not just a date.

Nic Brough -Adaptavist-

Hmm. You know, I'm not sure. I thought Due Date was a date-only field (but, be warned, I do not have a fantastic memory, it's more like one of those thingies with lots of holds in it

Technically, it's still a date/time field really, but date-only fields always store date+midnight, so your batch of issues due on the 2nd October 2021 would all have the same value that comes out in human as "2nd October 2021 00:00:00", and so your sort should be working off

The only database I've got access to to check this at the moment is a bit broken - I think I've pulled the disk cable out of the back of the pi that's running my database services during my attempts to tidy up the pile of computers in my study. I'll have a proper look tomorrow after I've worked out which disk(s) I've nudged out of place.

Jimmy Trivedi

Hi Nic,

Sure, I appreciate your hard work. Also if it is really date-time issue, then can you guide me any alternative way? Let's skip for Resolved case as of now. I'm interested in due date + priority sorting case.

Should I add any 3rd field or what? But the requirement is to first sort by due date and then priority wise.

Thanks.

Jimmy Trivedi

I solved using this answer: https://community.atlassian.com/t5/Jira-questions/Is-possible-ORDER-BY-two-fields-in-JQL-search/qaq-p/1313294

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

atl-gruland

jira-service-management-cloud

jira-service-management