• Icon: Suggestion Suggestion
    • Resolution: Answered
    • None
    • None
    • Standalone
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      I would really like to be able to use any Global Rank field type as the secondary sort on my Kanban boards. I can see this happening in one of two ways:

      1. Allow JQL statements like "ORDER BY priority DESC, Rank ASC", but require the user to specify the name of the rank field (possibly a prepopulated dropdown of the existing sorting fields in the query/filter). The problem with this approach is handling the UX for drag'n'drop reordering, which would be sensitive to the context of the primary sort.
      2. Create another Rank field type, or allow the current one, to default to a particular value (like 0 or the maximum integer value) instead of auto-incrementing the value each time an issue is created. This would allow the system to treat sorting statements the same - "ORDER BY Rank ASC, priority DESC" - while allowing a "default" ranking to take place until the rank value is set (by dragging and dropping a card higher on the list)

          Form Name

            [JSWSERVER-8486] Allow Rank field to be used as a secondary sort parameter

            Ordering should be able to work like this and it's extremely annoying that you don't allow this.
            For example in our case. We want to have unassigned tickets with state "in review" at the top so they are the first thing eveyone sees and can take care of them. At the same time I want to be able to order unassigned tickets by rank (drag and drop). It's annoying that it's not possible

            Petr Kučera added a comment - Ordering should be able to work like this and it's extremely annoying that you don't allow this. For example in our case. We want to have unassigned tickets with state "in review" at the top so they are the first thing eveyone sees and can take care of them. At the same time I want to be able to order unassigned tickets by rank (drag and drop). It's annoying that it's not possible

            Hello,

            What is the status of this at the time being? I understand it was not on Atlassian's roadmap in 2014 but maybe could be considered now, since looking through the internet and the comments above I still see a demand for it. In my business context, it would also help a lot in managing backlog.

            Adrian Łabęcki added a comment - Hello, What is the status of this at the time being? I understand it was not on Atlassian's roadmap in 2014 but maybe could be considered now, since looking through the internet and the comments above I still see a demand for it. In my business context, it would also help a lot in managing backlog.
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3070312 ] New: JAC Suggestion Workflow 3 [ 3662774 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2626729 ] New: JAC Suggestion Workflow [ 3070312 ]

            Sam added a comment - - edited

            +1 this would be extremely useful, and it's pretty unexpected it's not already supported. We'd also like to use "ORDER BY priority DESC, Rank ASC."

            Right now, anything with a "high" priority appears in a seemingly random order. Why not allow users to be able to choose rank within priority groupings?

            Sam added a comment - - edited +1 this would be extremely useful, and it's pretty unexpected it's not already supported. We'd also like to use "ORDER BY priority DESC, Rank ASC." Right now, anything with a "high" priority appears in a seemingly random order. Why not allow users to be able to choose rank within priority groupings?

            Elisa Abedrapo added a comment - - edited

            How has this been resolved? We need to get our backlog of about 100 items grouped by priority and with the ability to move them from the Backlog into the To-Do list in the Backlog screen.

            I tried the suggested approach (ORDER BY priority DESC, ORDER BY Rank ASC) and also (ORDER BY Rank ASC, ORDER BY priority DESC) and none of them work as we expected:

            • With the first query (ORDER BY priority DESC, ORDER BY Rank ASC) all our items are sorted by priority so they're nicely grouped as we need. However we're unable to move items in the Backlog screen into the To-Do list and the right-click menu on items don't show the options to move them either.
            • With the second query (ORDER BY Rank ASC, ORDER BY priority DESC) we got back the ability to move items in the list and into To-Do but of course the list doesn't respect priorities anymore, so we have to manually sort them out with it's really annoying.

            I can't upvote this ticket, I guess it's because it has been marked as resolved, but as my experience shows it still doesn't work.

            The answer from @mtokar (JIRA Agile Team) was over 4 years ago and given I found several other threads in Internet from teams who are struggling with this very thing and asking if there is any sort of workaround, I'd like to know if Atlassian has reconsidered including this feature for the near future.

            Thanks!

             

            Elisa Abedrapo

            J. Walter Thompson Co.

            Application Support Coordinator & Test Lead

            Portfolio & Solutions Team.

             

            Elisa Abedrapo added a comment - - edited How has this been resolved? We need to get our backlog of about 100 items grouped by priority and with the ability to move them from the Backlog into the To-Do list in the Backlog screen. I tried the suggested approach (ORDER BY priority DESC, ORDER BY Rank ASC) and also (ORDER BY Rank ASC, ORDER BY priority DESC) and none of them work as we expected: With the first query (ORDER BY priority DESC, ORDER BY Rank ASC) all our items are sorted by priority so they're nicely grouped as we need. However we're unable to move items in the Backlog screen into the To-Do list and the right-click menu on items don't show the options to move them either. With the second query (ORDER BY Rank ASC, ORDER BY priority DESC) we got back the ability to move items in the list and into To-Do but of course the list doesn't respect priorities anymore, so we have to manually sort them out with it's really annoying. I can't upvote this ticket, I guess it's because it has been marked as resolved, but as my experience shows it still doesn't work. The answer from @mtokar (JIRA Agile Team) was over 4 years ago and given I found several other threads in Internet from teams who are struggling with this very thing and asking if there is any sort of workaround, I'd like to know if Atlassian has reconsidered including this feature for the near future. Thanks!   Elisa Abedrapo J. Walter Thompson Co. Application Support Coordinator & Test Lead Portfolio & Solutions Team.  
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2327960 ] New: Confluence Workflow - Public Facing v4 [ 2626729 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2044826 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2327960 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2033173 ] New: JIRA PM Feature Request Workflow v2 [ 2044826 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 736631 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2033173 ]

              Unassigned Unassigned
              9dc4ab79ed4c mikeada
              Votes:
              3 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: