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

Sorting by Status is not working ?

Corinne Guibert_lao912

I want to display all the stories in one project and have them grouped by status.

I tried to use the "group by" jql command: not working

I tried to sort by clicking on the column name: not working as well

See screenshot below.

I don't understand why a task as simple as sorting by status cannot be done.

One project, one workflow so no confusion is possible.

Does anyone have any idea on what is happening ?

Thanks for any inputs

Capture d’écran 2025-07-16 110710.jpg

Accepted answers

All comments

Cyrille Martin

Hi @Corinne Guibert

Does your filter return only Stories ? or also sub-tasks ?

If there are sub-tasks then they will be displayed below their parent Story issues.

Just a question to better understand what is happening.

Regards,

Dave Mathijs

Hi @Corinne Guibert which View are you using to sort this column? List, All work, Search, ...?

Corinne Guibert_lao912

Hello @Dave Mathijs

I'm using the Search Work item menu

I have the same problem when I'm using the order by command and display the result in Confluence

Dave Mathijs

Can you share the Filter you are using?

Swathi Acharya

Hello @Corinne Guibert

Welcome to Atlassian Community!

Are you filtering Stories from a Team-managed projects?

Please note that the sorting of statuses in a Team-managed project is done by the sequence ID in the database assigned to the statuses at the time of creation. Some of the statuses may not have a Sequence ID assigned due to which they are not sorted as expected in the Issue navigator.

We do have a Feature request opened for the same here: https://jira.atlassian.com/browse/JRACLOUD-81149.

Thank you!

Corinne Guibert_lao912

Hello @Swathi Acharya

No, it's a team managed project.

And my concern is not about the sequence. My concern is that I should see all Development ticket together, all Frozen ticket together. Not a mix of status

The sorting part is simply not working

Corinne Guibert_lao912

@Cyrille Martin

Only stories, no sub-tasks

Corinne Guibert_lao912

@Dave Mathijs

See screenshot below. I'm getting all PRODUCT from a specific Epic Capture d’écran 2025-07-16 121335.jpg

Trudy P Claspill

Hello @Corinne Guibert

So far I have not been able to recreate your scenario.

Do other people have the same experience with the same filter?

Do you have the same experience if you filter based on another Company Managed project, or another issue type?

Have you tried a different browser app, a private browser window, or clearing your cache? Sometimes a browser cache issue can have strange impacts.

Corinne Guibert_lao912

Hello @Trudy P Claspill

I tried with a company managed project and another issue type and I have the same issue: status are mixed

Capture d’écran 2025-07-17 144702.jpg

I am using this filter in a Confluence page and one colleague reported sorting problem (in fact this is when I realized there was something wrong: she asked me to have the issues sort and I realized that it should already be the case)

I used Chrome to run the same filter (first connexion to Jira with Chrome so no cache issue) and the problem is the same. As stated Cyrille, it seems that the sort is done using the Key and not the status, despite what is written in the request and the fact that I used the UI to specify the sort filter (clik on the header column)

Trudy P Claspill

Thank you for that additional information @Corinne Guibert

At this point I recommend that you open a support case directly with Atlassian. If you are not an Administrator for Jira you may need to contact your Jira Administrators o have them open the support case.

https://support.atlassian.com/contact/#/

Atlassian will be able to look at backend and database information to try to find the root cause.

I have seen this problem reported in the forum a few times, but no solution information has been posted.

If Atlassian can provide you with root cause and solution information it would be great if you would share that information back here with the community.

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