What purpose does this combination serve?
I use 'key <=' and 'key >=' in queries all the time.
I sort by type pretty frequently.
I can still sort by key or type if I type in the JQL, but not by clicking a column header.
This multi-click filter setup is annoying, and it's on the 'All Work' tab, but not the 'List' tab.
'All Work' should be the more tabular / less hand-holding view, IMNSHO, and there is no value to the end user to aggregating these columns.
Hi @Anne Saunders,
I tend to agree to your statement. It is not something that you seem to be able to disable. As you noted, sorting directly in JQL still works, luckily.
I would consider providing your feedback directly to Atlassian through the in product feedback feature.
Hope this helps!
I have submitted my feedback. I really cannot believe this is what passes for any kind of improvement.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Under the ellipse menu, there's an option to toggle to the "old search", which I have enabled.
Changing it did give me the hateful banner message that this is coming for good in November.
I'm so so so sick of "improvements" that aren't.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This does not fix the search from within a project context.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.