• 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)

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

            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 ]
            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 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Martin (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 526914 ] New: JIRA PM Feature Request Workflow v2 [ 736631 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Major [ 3 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Michael Tokar made changes -
            Resolution New: Answered [ 9 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            mikeada created issue -

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

                Created:
                Updated:
                Resolved: