When I get into the Issue Navigator for a project I see the issues sort according to Priority by default. We don't really use Priority in our projects, so it's annoying to have to select a new field (which I can't scroll to, btw) and then re-select the ordering, and THEN, if I'm lucky, I don't have to change the filter, otherwise the view defaults to sorting by Priority.
I can't find any documentation on how to configure this setting. I want to be able to have the issues sort by Key, descending, when I open the Issue Navigator. Anyone know if there's a way to make that happen? Thanks!
This is COMPLETELY Stupid
I have to track mulitple projects on an hourly basis, and having to change "priority" to "key" each time I want to view latest issues is a waste of productivity and amounts to a definate COST to the company as the time it takes to do this is multiplied across engineers PMs etc.
As a system admin, if I can change the way boards and screens are displayed, why can't a user profile have the ability to assign their default "issue" order without having to create a filter to do so.
This should be an easy feature to provide considering how configurable JIRA is.
Atlassian please don't address your customer base needs like MS does.
The dropdown list next to the default Order by Priority is demented. Over 300 items. A small handful (7-10?) of common-sense frequently used options such as by Date, by Issue number, etc. listed in a separate section at the top of the list would definitely help Jira users.
I'm with John and all the rest above: This is stupid. I deal with it every day and find no reason in the world that priority should be the default. If they can make it configurable then for all the money we are paying for this stuff they need to hire a programmer that can fix this issue.
Not sure jumping on helps -- but I just researched this and found 3 other threads asking for this very same feature - the ability for a user to set the default issue sort.
This one looks like a pretty needed and handy feature. Maybe look at items like this that make your existing tool better vs. doing full rewrites of tools that muck up things like projects beyond recognition.
I'm an avid Jira user since early 2016 and have been watching this thread. I can't understand why Support cannot fulfill such a seemingly simple request with all the people that are out there asking about it. Forgetting for a minute all the people asking for a change, it simply defies logic to have coded it the way it is right now anyway. All I can think to do is pile onto the list of those complaining about it so maybe they will listen.
I voted. But, after two years, it is seeming to need a "midterm election" to break the stalemate. Does Atlassian have those? :) It could be admitting, indirectly, there is something too embedded to be worth fixing to them; a shame. They should, because it kills their customer's productivity, and is very frustrating. I've wasted so much time screwing with this menu. The last time I got a support ticket done they were timely, persistent on verifying my resolution, pleasant, and pretty much custom-fixed my situation. For the record, however, it was a bug already. This is no different, with the exception of the extreme "popularity", so I don't understand why there is no adequate explanation despite all the votes on that link, other than to speculate a bit more as I have done already.
Over the next several weeks we'll be sharing some of our Getting Started guides here in the community. Throughout this series of posts, we'd love to hear from customers and non-customers ab...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs