• Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Icon: Low Low
    • None
    • None
    • None
    • None

      Problem Definition

      When a Jira administrator is re-ordering a status using the arrows in the order column of the "Statuses settings screen" this did not reflect in the issue view status order.

      Environment

      • Cloud.
      • New issue view.

      Suggested Solution

      The order chosen in the "Statuses settings screen" gets reflected.

      Why this is important

      • Using the order arrow is a valid way to organize the output.
      • Currently, an Admin cannot choose an order for the status in the issue view.

      Workaround

      • Currently , I could not find any workaround.

        1. screenshot-1.png
          screenshot-1.png
          110 kB
        2. screenshot-2.png
          screenshot-2.png
          148 kB

            [JRACLOUD-72069] As a Jira admin I want to re-order statuses in the new issue view

            Matthew Canham made changes -
            Assignee Original: Matthew Canham [ 90b1f9a97277 ] New: Ahmud Auleear [ 2239430e27fb ]

            Timothy Cook added a comment - - edited

            Looks like if you follow this process you can impact the order by adding the `opsbar-sequence` property values: https://community.atlassian.com/t5/Jira-questions/Changing-Order-of-the-Workflow-Transition-Buttons/qaq-p/239379

             

            That said, it's very confusing and not well-documented, especially given this button/dropdown is the most prominent feature on Jira  

            Timothy Cook added a comment - - edited Looks like if you follow this process you can impact the order by adding the `opsbar-sequence` property values:  https://community.atlassian.com/t5/Jira-questions/Changing-Order-of-the-Workflow-Transition-Buttons/qaq-p/239379   That said, it's very confusing and not well-documented, especially given this button/dropdown is  the most prominent feature on Jira  

            Sébastien added a comment - - edited

            The ordering logic is not impacted at all by the order of statuses in the status settings screen.

            Why???

            The purpose of the ticket was to be able to reorder. How can we reorder statuses?

            Sébastien added a comment - - edited The ordering logic is not impacted at all by the order of statuses in the status settings screen . Why??? The purpose of the ticket was to be able to reorder. How can we reorder statuses?
            Matthew Canham made changes -
            Assignee New: Matthew Canham [ 90b1f9a97277 ]
            Matthew Canham made changes -
            Status Original: Open [ 1 ] New: Closed [ 6 ]

            Hi everyone,

            My name is Matt, I'm a product manager on the Jira Cloud team.

            This issue has now been resolved by the honoring of the opsbar-sequence transition property in the new issue view (JRACLOUD-70702).

            The approach we have taken will only affect the ordering of transitions within the new issue view. Nothing will change in the old issue view. The ordering logic is not impacted at all by the order of statuses in the status settings screen. The ordering logic is as follows:

            • Always show transitions with the opsbar-sequence property first according to their opsbar-sequence value (lower values appear first)
            • Then show remaining transitions ordered first by category (Todo, In Progress, Done)
            • Within category order alphabetically by name of the status being transitioned to

            Thank you all for your support and patience as we worked on this. Please don't be afraid to share any stories or workflow improvements that this allows so that they can be fed back to the team.

            Matthew Canham added a comment - Hi everyone, My name is Matt, I'm a product manager on the Jira Cloud team. This issue has now been resolved by the honoring of the opsbar-sequence transition property in the new issue view ( JRACLOUD-70702 ). The approach we have taken will only affect the ordering of transitions within the new issue view. Nothing will change in the old issue view. The ordering logic is not impacted at all by the order of statuses in the status settings screen . The ordering logic is as follows: Always show transitions with the opsbar-sequence property first according to their opsbar-sequence value (lower values appear first) Then show remaining transitions ordered first by category (Todo, In Progress, Done) Within category order alphabetically by name of the status being transitioned to Thank you all for your support and patience as we worked on this. Please don't be afraid to share any stories or workflow improvements that this allows so that they can be fed back to the team.
            Matthew Canham made changes -
            Status Original: Closed [ 6 ] New: Open [ 1 ]
            Matthew Canham made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]
            Earl McCutcheon made changes -
            Link New: This issue duplicates JRACLOUD-70702 [ JRACLOUD-70702 ]

            I This is simply lost functionality = a bug.  The workaround is time consuming and unnecessary: the data to implement the fix is currently embedded in the workflows.  Please make use of it.

            Mark Hanson added a comment - I This is simply lost functionality = a bug.  The workaround is time consuming and unnecessary: the data to implement the fix is currently embedded in the workflows.  Please make use of it.

              2239430e27fb Ahmud Auleear
              fabbes Fares Abbes (Inactive)
              Votes:
              42 Vote for this issue
              Watchers:
              37 Start watching this issue

                Created:
                Updated:
                Resolved: