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

"Allow issue ranking" returns error - "We couldn't update your board filter

Heidi Aspell_6f9vg2

I have a new board with a new filter, and by default it seems that "ISSUE RANK ON BOARD" is disabled.

On the board General Settings screen, under "Filter details" there is an "Allow issue ranking" button. However, when I click this button I get an error.

"We couldn't update your board filter"

I am the owner of the filter, and the project has view permissions for the filter across all roles.

What am I missing? Is there a specific permission hidden somewhere that I need to grant?

Accepted answers

Heidi Aspell_6f9vg2

Figured it out myself eventually. I manually edited the filter to "project in (SUS,BA) ORDER BY Rank ASC".

Seems to be a Jira bug that the button to toggle on ranking doesn't work in all scenarios.

All comments

Bharat

hi @Heidi Aspell - Welcome to the community. It seems like a bug or a one time glitch…I could be wrong but have you tried it again? Also, I think you should open a support ticket because the error is very generic to tell us what is failing.

Thanks,

Bharat

Heidi Aspell_6f9vg2

Figured it out myself eventually. I manually edited the filter to "project in (SUS,BA) ORDER BY Rank ASC".

Seems to be a Jira bug that the button to toggle on ranking doesn't work in all scenarios.

Heidi Aspell_6f9vg2

I tried many times, refreshed the browser, cleared the cache...

Tomislav Tobijas

Hi @Heidi Aspell ,

Can you check who is listed as the filter editor? That might be causing the issue here.

As for ranking, what this "Allow issue ranking" actually does is change the end of the filter query by adding/replacing part ORDER BY Rank ASC

*before selecting "Allow issue ranking"

*after selecting "Allow issue ranking"

It should work even in your case and it would replace "DESC" with "ASC" ordering/sorting way.

Anyway, even with this left as-is, ranking would work but it might not be the best practice (again, this kinda depends on the use case).

Cheers,
Tobi

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-cloud