1 click sorting gone - Work item (summary, issue type, key) now all aggregated in a column

[Danise Alano-Martin]

With the new automatic aggregation of Issue type, Key, and Summary into the same sortable column in a filter, it now takes 3 clicks to sort by those things (so 9 clicks if I want to view my filter each way), instead of 1 click per. 

Is there a setting somewhere where I can default to each of those being in their OWN column again instead of concatenated? If not, this is a 200% increase in overhead for searches I and other product owners do multiple times a day.

[Karan Sachdev]

Hey @Danise Alano-Martin

Welcome to Atlassian Community!

This is a new roll out that started last week. You should be able to sort based on one of these 3 values using the options as in your screenshot.

Alternatively, you can still use the "ORDER BY" clause in JQL to sort based on one of these.

I understand this is less convenient as compared to the previous column configuration. I'll try to contact the concerned team internally and will share your feedback.

However, if you feel this breaks a functionality or if you need further assistance, please feel free to log a support ticket and the team will further help you.

Thanks!

[Danise Alano-Martin]

Appreciate your response and acknowledgment of the inconvenience. And I appreciate you sharing feedback with Atlassian design team.

[pawarsachin84]

Hello @Danise Alano-Martin ,

Welcome to the Atlassian Community! 

To better understand your use case — could you clarify:

1. Are you referring to sorting from a Jira issue filter/search result, or viewing child issues (e.g., sub-tasks, linked issues) inside the parent issue view?

2. Are you working in full-screen mode on a desktop, or might this be constrained by screen size or windowed view?

Configure the default All work navigator

Update issues right from the list view

There was support ticket raised JRACLOUD-80784

[Danise Alano-Martin]

Thanks for asking. 

Question 1 - I don't see any differences when looking at child issues inside the parent view (see screenshot) vs Jira issue filter/search in my original report, so my answer is it's an equally inconvenient 200% increase in clicks now in both views. 

Question 2 - full-screen, desktop. Screen size is not a factor.