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

Order by the same ticket order as shown in the "IN" clause

Mohamad Ibrahim_a92mgg

Hello,

I have a JQL that has an "IN" clause which contains a list of jira tickets IDs. I want to show this list of returned jira tickets in the same order as listed in the "IN" clause. Here's the JQL script:

id in (PENNY-2852, PENNY-2853, PENNY-2854, PENNY-2855, PENNY-2856, PENNY-2857, PENNY-2858, PENNY-2860, PENNY-2861, PENNY-2862, PENNY-2863, PENNY-2864, PENNY-2865, PENNY-2866, PENNY-2867, PENNY-2868, PENNY-2872, PENNY-2873,PENNY-2898,PENNY-2896,PENNY-2897,PENNY-2913,PENNY-2912,PENNY-2935,PENNY-2911,PENNY-2934,PENNY-2915,PENNY-2933,PENNY-2914) "

ORDER by key does not help much as the tickets could be created in any random order but the order mentioned in the "IN" clause should be maintained. How can I achieve that?

Accepted answers

All comments

Nic Brough -Adaptavist-

There's no way to do that. Your "in" clause has nothing to do with ordering.

You'll need to look at other data on the issues for your sort.

Mohamad Ibrahim_a92mgg

Why tickets are not ordered by the same order sent in the "in" clause should not be the case? Any suggested workarounds?

Nic Brough -Adaptavist-

Why would they be?

A question asking for a list of issues is one thing. How you display it (including the sort order if one even applies in your result report) is another thing.

You'll need to look at something else to do the ordering.

dkamath

Sambit Mishra_mw3t1k

I see this as a very valid and common sense requirement. I expect the query to return me back a report exactly in the same order as my input queue is. I didnt expect jira to apply a default ordering I never asked.

The use cases are far reaching and very relevant for collabs - I may get a input stream of data from any source and post my specific query processing - the order if maintained is a simple match key option / or match sequence - than an elaborate post or pre-processing i need to do now - just because JIRA defaulted to some ordering which was never asked.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

jql