Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-21328

Improvement to transition ordering introduced in 4.1

    XMLWordPrintable

Details

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

    Description

      In 4.1.1, the ability to reorder transition steps was added, per JRA-5789. The method to do so is to add a property to each step called "opsbar-sequence" - the integer values of this property define the order in which the steps will appear.

      While this DOES work, it definitely seems like the "cheap way" out, and is not easy to use. The workflow editor does not display items in this order, so from here you have no idea if the order is correct. Only by publishing and going to an issue in the appropriate step can you confirm the ordering.

      It would be MUCH more usable to either have a "drag-and-drop" (as was mentioned in the other issue after it was released), or maybe even simply some "up and down" arrows that allow me to reorder the steps. A button to sort the list alphabetically (or reverse alphabetically) would probably also be useful for some users.

      Why should I care what some arbitrary integer value is of the step after the one I'm interested? To the user, that does not matter and gets complicated very quickly - especially if there are a decent number of transition steps involved. What matters is that I want step A to appear after step B - that's all. If JIRA wants to assign arbitrary integers based on how I order them in the UI, so be it. But that is an internal implementation detail, not something to be exposed to the user.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              f4dbbf95e48a Adam Clauss
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: