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; } } }

Is it possible to group issues with JQL where I can indicate the order(other than DESC or ASC)?

Carlos Garcia Navarro

Hi, I want to create a filter in JIRA that orders the issues by status and by date of creation. My JQL looks something like this: "issuetype = D-patch order by status, created". What I really want is to group the different issues by status and then order them by date of creation. My query will do that, but will use alphabetical order for the status. Is there a way to indicate the order I want for the status? e.g. to show the results group by status following this order "In Queue", "In Progress", "Need more information", "Done", "Resolved", and for each group the issues are ordered by creation date.

Thanks!

Carlos

Accepted answers

Ignacio Pulgar

Hi Carlos,

Good news! You'll be able to achieve what you want.

Fortunately, the Order By clause doesn't order the Status field alphabetically.

You can decide the order of statuses from:

<your Jira URL>/secure/admin/ViewStatuses.jspa

Just click on the up/down arrows to order the statuses as per your needs:

After that, "ORDER BY status ASC" will retrieve the same status order you had defined on that page.

Besides, this status order is also used in gadgets.

Hope it helps.

All comments

Mathieu Yargeau_f60wor

I am sorry to say this, but it cannot be done. Here is the clause documentation:

https://confluence.atlassian.com/jirasoftwarecloud/advanced-searching-keywords-reference-764478340.html?_ga=2.171645152.155989567.1516640638-4443214.1497379260#Advancedsearching-keywordsreference-ORDER_BYORDERBY

Nic Brough -Adaptavist-

JQL is not the same as SQL. It does not return data or say anything about how to present it. It simply gives back a list of issues that match.

It is up to the presentation code running the search to decide how to display it. The issue navigator does not support grouping. Some reports do, but they do it in themselves, they don't look at the search.

The "order by" clause is the only exception - it is used by *some* code that runs searches for ordering when it matters (boards and the issue navigator are the two that spring to mind when someone asks what might use it, and I think a couple of gadgets and reports use to too)