Summary

      When defining the status order for an agile board in Configure > Column Management ,
      the order is not reflected in the board accordingly

      Steps to Reproduce

      1. Open an Agile Board
      2. Configure > Column Management
      3. Configure as below

      Expected Results

      When viewing in the board , it should follow the order of the status configured in column management

      Actual Results

      The order is not followed.

      Workaround

      The status order on the column follow the step id of each issue's workflow. Steps with a lower id will appear on top than those with higher (later) ids.
      A workaround to edit the steps' ids has been published on this KB:

      It consists of updating the descriptor column of the jiraworkflows table to change the content inside the XML representation of the steps' ids.

        1. board2.png
          board2.png
          7 kB
        2. column_management.png
          column_management.png
          13 kB
        3. kanban_view.png
          kanban_view.png
          12 kB

          Form Name

            [JSWSERVER-12944] Status in Board Column is not in Order

            Reproduces in the v9.12.18

            Viktoriia Boiko added a comment - Reproduces in the v9.12.18

            We also have this issue with one of our customers that the statuses are not sorted correctly within a Kanban board. However, I was able to find out what the problem is in our case. As soon as a condition is defined in a possible transition, the sorting is corrupted. If the condition is deleted, the sorting works as expected. 
            I have recreated the complete scenario in a fresh instance, where only Jira Core, JSW and JWM are installed and no additional apps are installed. There, I adjusted the default Kanban accordingly (see screenshot) and created a issue with which the behavior is easily understandable. I have also addressed the entire situation to Atlassian via a support ticket.
            Maybe the case is the same for one of you and helps you a little bit.

            https://jira.atlassian.com/browse/JSWSERVER-21576

            Frank Leclerc [Decadis AG] added a comment - - edited We also have this issue with one of our customers that the statuses are not sorted correctly within a Kanban board. However, I was able to find out what the problem is in our case. As soon as a condition is defined in a possible transition, the sorting is corrupted. If the condition is deleted, the sorting works as expected.  I have recreated the complete scenario in a fresh instance, where only Jira Core, JSW and JWM are installed and no additional apps are installed. There, I adjusted the default Kanban accordingly (see screenshot) and created a issue with which the behavior is easily understandable. I have also addressed the entire situation to Atlassian via a support ticket. Maybe the case is the same for one of you and helps you a little bit. https://jira.atlassian.com/browse/JSWSERVER-21576

            Matt Doar added a comment -

            Confirming that this is not fixed for us in Jira Software DC 8.20.10

            Steps to Reproduce:

            1. Map two statuses into one column in an agile board in order StatusA, StatusB
            2. Drag an issue into that column in an active sprint
            3. Change the order of the two statuses in the column to StatusB (top), StatusA
            4. Drag an issue into that column in an active sprint

            Expected: the two statuses would shown in the order StatusA, StatusB. Then after step 3, the two statuses would shown in the order StatusB, StatusA

            Actual: the order of the two statuses is unaffected by their order in the Columns page

            Matt Doar added a comment - Confirming that this is not fixed for us in Jira Software DC 8.20.10 Steps to Reproduce: 1. Map two statuses into one column in an agile board in order StatusA, StatusB 2. Drag an issue into that column in an active sprint 3. Change the order of the two statuses in the column to StatusB (top), StatusA 4. Drag an issue into that column in an active sprint Expected: the two statuses would shown in the order StatusA, StatusB. Then after step 3, the two statuses would shown in the order StatusB, StatusA Actual: the order of the two statuses is unaffected by their order in the Columns page

            Julien Rey added a comment -

            Hi 3d860f3e97e1,

            Sorry to hear that you are still impacted by the bug.

            Can you please raise a support ticket via https://support.atlassian.com/, so that the support team can investigate this issue?

            Julien Rey added a comment - Hi 3d860f3e97e1 , Sorry to hear that you are still impacted by the bug. Can you please raise a support ticket via https://support.atlassian.com/ , so that the support team can investigate this issue?

            It still doesn't work in 8.13.13 as well. 

            MEDITECH ADMIN TEAM added a comment - It still doesn't work in 8.13.13 as well. 

            This appears to be broken in 8.13.11? I've tried changing the order of statuses in the board config but this has no effect when moving issues in the board. Guess no one will read this as it's a closed issue though. 

            Ben Robbins added a comment - This appears to be broken in 8.13.11? I've tried changing the order of statuses in the board config but this has no effect when moving issues in the board. Guess no one will read this as it's a closed issue though. 

            The workaround doesn't help people on cloud, though.

            John Worrall added a comment - The workaround doesn't help people on cloud, though.

            Rodrigo Martinez added a comment - - edited

            Hi people!

            A workaround KB's just been published for this issue:

            It consists of updating the jiraworkflows table to change the steps' ids of the affected workflow. Other than this, the steps' ids can only be changed by recreating them in the desired order on the same or a new workflow.

             

            Cheers!

            Rodrigo Martinez added a comment - - edited Hi people! A workaround KB's just been published for this issue: How to reorder statuses on board columns in Jira It consists of updating the jiraworkflows table to change the steps' ids of the affected workflow. Other than this, the steps' ids can only be changed by recreating them in the desired order on the same or a new workflow.   Cheers!

            I looked at the affected workflow and think it could be the action id numbers e.g.

            <action id="211" name="Cancelled">
            

            ... vs.

            <action id="331" name="Delivered on Prod">
            

            ... even though the board prioritizes Delivered over Cancelled FYI

            Arraaf Mochny added a comment - I looked at the affected workflow and think it could be the action id numbers e.g. <action id= "211" name= "Cancelled" > ... vs. <action id= "331" name= "Delivered on Prod" > ... even though the board prioritizes Delivered over Cancelled FYI

            When will this issue be addressed?

            Shaun Hazard added a comment - When will this issue be addressed?

              cf7069360d7e Mateusz Witkowski
              amasut Azfar Masut (Inactive)
              Affected customers:
              81 This affects my team
              Watchers:
              70 Start watching this issue

                Created:
                Updated:
                Resolved: