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

Changing the default order in the issue navigator without adding a sort by clause?

Contact Kintosoft

Hi,

It looks like the Issue navigator overrides the order of the issues returned by JQL queries by adding some default criteria.

of course, I can force the order by adding an ORDER BY <some value> clause, but is it possible to get the same order than the original returned by JQL functions?

Thanks,

Pablo

Accepted answers

All comments

Nic Brough -Adaptavist-

I'm a bit confused here. If you run JQL with "order by", it comes into the navigator. If you run it without, it uses the default. But what you're asking for is "the same order that the JQL returns it". But unless you put in an order by clause, JQL doesn't actually have an order, it's a list of issues. So what you're asking for is to order a list without specifying any order?

Contact Kintosoft

Yes, I would like the Issue Navigator respect the same order than the list.

A real case, The Links Hierarchy plugin exports all the issues in the tree:

issue in (AS-12,AS-4,AS-40,AS-65,AS-49,AS-50,AS-51,AS-52,AS-53,AS-54,AS-170)

by using the first-depth algorithm to get the issues in the hierarchy and make the issue key list above.

An user wants to see the same order AS-12, AS-4, etc in the Issue Navigator. Unfortunetely, there is not any custom field that can be used in the ORDER BY clause to get the "hierarchical" order, and the user gets an unexpected/undesired value.

Nic Brough -Adaptavist-

You've missed my point. The list returned by JQL does not have an order.

You haven't said "order by", so you just get the unsorted list. It's irrelevant what the user typed in, JQL has no results order unless you add an order by clause (and that only kicks in when you're using something that uses it).

What you need to do is write a JQL function that allows you to say "order by what the user typed in". But I can see that getting immensely painful for complex or long queries.

Contact Kintosoft

The list returned by JQL does not have an order.

I do not agree. Below is the getValues standard function returning values for a JQL function:

public List&lt;QueryLiteral&gt; getValues(			 QueryCreationContext queryCreationContext, FunctionOperand operand,
			TerminalClause terminalClause){

...

}

It returns a java List object, so plugins can return ArrayList instances which are ordered. However, JIRA overrides this order at some point...

What you need to do is write a JQL function that allows you to say "order by what the user typed in". But I can see that getting immensely painful for complex or long queries.

Absolutelly agree. Even more, sometimes JQL results cannot be sorted by using an ORDER BY clause... another real example: Subversion ALM can return latest commits. It would be nice see them from newer to older in the Issue Navigator, however, JIRA overrides the order and users cannot sort by commit date as this is not a custom field, it is an internal data/attribute.

IMHO JIRA sould not re-order the results by default if an ORDER BY is missing or support some instructions/command/parameter to force the Issue Navigator to respect the original.