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

Problems with Active Sprints display order when not using Rank and Quick Filter is active

Brian Carl

We're not using the Jira default Rank for our board as we've got various business reasons for needing enter-a-value control over our backlog ranking/order.

That being said, the Active Sprints list displays in the correct order until we enable a Quick Filter (mostly used to focus in on a particular Assignee). With any Quick Filter enabled, the Active Sprint display order is apparently random.

I've tried manually syncing the Jira Rank values to match the order of our custom order field, but that doesn't seem to help.

Other ideas?

Accepted answers

All comments

Ismael Jimoh

My understanding of your problem is that you are not ordering your board filter by the rank field but instead another field.

However, when you enable a quick filter, it it breaks the order.

Firstly, canyou confirm I understood the problem?

Secondly if you do not currently use an order by feature on the filter, I will strongly advise you do.

If the second has been done but you still experience product, can you order your quick filters by the same field and confirm if the problem persists?

Brian Carl

Thanks for the comment and ideas, Ismael.

You have correctly summarized the problem.

I have tried adding an ORDER BY clause to my Quick Filter definitions and that doesn't help - the order is still random.

Detail:

Board Filter Query: project = ONE10PLAT ORDER BY "Team Priority" ASC

Quick Filter (adjusted): assignee = "Eric Dobrzelewski" ORDER BY "Team Priority" ASC

With the Quick Filter disabled, ONE10PLAT-3195 shows at the top (Team Priority = 10). When the Quick Filter is enabled, ONE10PLAT-3304 shows at the top (Team Priority = 30)

Ismael Jimoh

That’s odd.

Can you make the following change and reindex (seeing as Rank field uses unique charcters to sort, it might help)

your search order by your field, rank asc

This should force some more restrictions on the ordering.

Before that check what searcher the field Team Priority uses. When a search is behaving funny I will start with this and also index the application.

Brian Carl

Thanks, Ismael.

I added Rank to the ORDER BY clause (both for the board filter and the quick filter) and it didn't help.

I don't know how to reindex my project. I looked for instructions on this, but it seems like it's been removed in the version of Jira we're using:

https://community.atlassian.com/t5/Jira-questions/re-index-project-in-the-new-Jira-UI/qaq-p/700115

Also, I'm not clear how to determine "what searcher the field Team Priority" uses. Can you be more specific?