Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-9675

Ability to order statuses within columns

XMLWordPrintable

    • 0
    • 6
    • 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.

      NOTE: This suggestion is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding suggestion.

      It would be great if we could change the order of the statuses in a particular column, in work mode.

      Consider the following scenario:

      Column 1, 2 , and 3
      Column 1 has status "Open" and "Reopened"
      Column 2 has status "In Progress"
      Column 3 has status "Resolved" and "Closed"

      When transitioning something from Column 2 to Column 3, dragging the issue and hovering over column 3, "Resolved" is displayed on top and "Closed" on bottom. However, if we change this configuration in to display the contrary (Resolved = bottom, Closed = top) and go back to the board, it doesn't obey the configured order - it always seem to display the columns on a pre-defined order.

          Form Name

            [JSWSERVER-9675] Ability to order statuses within columns

            Eli Mata added a comment -

            There is a workaround, however, it is very labor intensive and likely not a good solution. The order in which transition state (aka step) depends on its Step ID.  For example, if I have the following transition steps with the following ids, "Send to Dev Lead (5), Send to QA (7)", "Send to QA (9)", " it will show the ones with the highest ID at the TOP of the column and go in largest to smallest order.  The ids are given when a transition state is created. If i want to have "Send to Dev Lead" first (at the top) I need to delete it and then recreate so it can get a new higher id. This becomes very cumbersome if you need to move several transitions around.

            So if you are looking at a column on a board and add a new state that state will show up at the TOP of the column and not the BOTTOM.

            Eli Mata added a comment - There is a workaround, however, it is very labor intensive and likely not a good solution. The order in which transition state (aka step) depends on its Step ID.  For example, if I have the following transition steps with the following ids, "Send to Dev Lead (5), Send to QA (7)", "Send to QA (9)", " it will show the ones with the highest ID at the TOP of the column and go in largest to smallest order.  The ids are given when a transition state is created. If i want to have "Send to Dev Lead" first (at the top) I need to delete it and then recreate so it can get a new higher id. This becomes very cumbersome if you need to move several transitions around. So if you are looking at a column on a board and add a new state that state will show up at the TOP of the column and not the BOTTOM.

            Francesco Fragomeni added a comment -

            I would love to see something happen here especially considering that reordering statuses in a column via the opsbar-sequence is now broken due to a bug (https://jira.atlassian.com/browse/JSW-13864?workflowName=JIRA+Bug+Workflow+w+Kanban+v6&stepId=1). Really hope that someone pays attention to these issues considering that the only way to do this now doesn't work.

            Francesco Fragomeni added a comment - I would love to see something happen here especially considering that reordering statuses in a column via the opsbar-sequence is now broken due to a bug ( https://jira.atlassian.com/browse/JSW-13864?workflowName=JIRA+Bug+Workflow+w+Kanban+v6&stepId=1 ). Really hope that someone pays attention to these issues considering that the only way to do this now doesn't work.

            Matt Patey added a comment -

            The problem I have is that a transition's ID is used to determine the order of the statuses on my board.

            A sorting key similar to opsbar-sequence could be a viable solution, though for boards with many transitions, it would be somewhat cumbersome.

            Matt Patey added a comment - The problem I have is that a transition's ID is used to determine the order of the statuses on my board. A sorting key similar to opsbar-sequence  could be a viable solution, though for boards with many transitions, it would be somewhat cumbersome.

            Denis Blanchette added a comment -

            It would be more logical that "Completed" be over "Rejected" on our board. I agree with this suggestion.

            Denis Blanchette added a comment - It would be more logical that "Completed" be over "Rejected" on our board. I agree with this suggestion.

            Robin added a comment -

            The similar point is another issue, sadly rejected by Atlassian: GHS-11639.

            Robin added a comment - The similar point is another issue, sadly rejected by Atlassian: GHS-11639 .

            Niels Massink added a comment -

            We agree. (We are currently evaluating this for a customer)

            I would even like to add that we don’t only want to order
            them but also want to have a separator or something between them. (We want to
            make it visible what the current status is).

            A bit similar perhaps… I also noticed that when you drag the
            item you can chose which of the statuses you want to give that item when you
            move it to a new column. But it isn’t showing the other statuses of the current
            column.

            Niels Massink added a comment - We agree. (We are currently evaluating this for a customer) I would even like to add that we don’t only want to order them but also want to have a separator or something between them. (We want to make it visible what the current status is). A bit similar perhaps… I also noticed that when you drag the item you can chose which of the statuses you want to give that item when you move it to a new column. But it isn’t showing the other statuses of the current column.

              Unassigned Unassigned
              brosa Bruno Rosa
              Votes:
              14 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated: