Remember the last Issue sort per user (BB-4087)

Issue #3146 resolved
Parnell Springmeyer
created an issue

I find it really annoying that by default the issues are sorted by //date created// rather than //most important// (blocker, critical, major, etc...).

It's a super simple fix and it would be a lovely one to make!

Comments (34)

  1. Dylan Etkin

    Hi Parnell,

    Actually the issues list is sorted by creation date. I don't know about you but I find this to be the most useful default sort.

    Also the column headers are clickable and allow you to change the sort order.

    My instinct is to leave the sort as is but I am happy to hear arguments to the counter.



  2. Parnell Springmeyer reporter

    Yes you are right, it is by the creation date.

    I do use the column headers to change the sorting but I never ever actually use the sort by date - because to me, as an implementor, the importance of the ticket is of more immediate value to me than its creation date.

    I suppose it comes down to more of a preference thing - I guess some shops may care more about the creation date than the criticality of a ticket? I haven't worked in many but I do know TRAC sorts by criticality by default (most critical first, least critical last).

  3. Parnell Springmeyer reporter

    @David: true, I could do that if I wanted to; but that isn't entirely the point - should I ask all of my other collaborators to go create a bookmark of the issues query page just so that they can also all see the critical issues first? That seems silly to me, people on teams care about what's most important!! Not when something was first added (and when they do, it's probably once a month for ticket accounting purposes)!

    I'm also a programmer and I know it's easy to get stubborn about how something should be logically "ordered" (ordering by creation date sounds more logical from a programming perspective) however my experience with typical users (of whom are users of this issue system, my collaborators aren't programmers but they use the ticketing system to prioritize work and also see what's most important) says that the most important thing is the criticality of the ticket and not its creation date!!

    Heck, it took you guys long enough to add "importance" to tickets in the issue system! Before that we were putting "[high]/[med]/[low]" in our ticket titles to denote importance!!

    I love bitbucket man, but being stubborn doesn't necessarily make me want to stick around.

    What should really be done is the user should be able to configure the default behavior - but I assume adding that in has a much lower priority than many other projects so it isn't something that would happen very quickly.

  4. DurhamG

    Bumped. Why not make the page just remember the sort order the user last chose? Then everyone gets what they want. Every time I load the page I immediately sort by priority, which is a pain in the rear. Bookmarks are not the answer, but maybe allowing me to save queries (which would contain sort order) in a list on the issue tracker site itself would go a long way.

  5. Richard C
    • changed status to open

    I agree with DurhamG's suggestion - the issue tracker should remember sort order. This is my biggest annoyance with Bitbucket's issue system. Please make this a priority!

  6. Henrik Fridström

    +1 Im fine with people having other preferences as far as the defaul sorting goes but enforcing it back to this sorting even after I've changed it to my prefered way of sorting is very irritating. I'm surprised to see this issue having been aorund since 2011 without being fixed. Love the Product but this issue is very annoying to me.

  7. Richard Hall

    +1 Please make it remember both the last sort column, but also the results page it was on. At present if I sort by importance, then click on an issue on page 3 of the results for example, when I return to the issues tracker it takes me back to page 1 of the issues sorted by date. Ideally I would like to return to page 3 of the issues by importance if that's where I last had the issues tracker. This could be remembered in the back-end database against the session ID and should not be a massive undertaking.

  8. Log in to comment