Ability to Sort The Workflow Step Name ID Position

XMLWordPrintable

    • 0
    • 5

      Problem Definition

      The want to be able to easily sort the stepname ID of the workflow position as this then can allow the user to point to a default status when moving an issue from one project to another, in the current situations. When the user is doing the move issue from one project to another, the default status that is prompted is based on the very first stepname ID of the workflow, the user wants the ability to sort this and put a different stepname ID in the first position, so it's easier to pick as it will point to the first stepname ID by default, quickening the moving issue action for the user.

      Sample Picture

       The positioning of the status in the workflow:

       The positioning of the status in the Move Issue screen:

      Suggested Solution

      Allow the ability to sort the position of the stepname (id) in the workflow without affecting the workflow transition between one status to another. The sorting ability only affects the positioning of the status when appearing throughout the JIRA application dropdown menu from where the user can choose from.

      Why this is important

      This sorting ability, furthers speeds up the process/action that relies on choosing the status of the workflow from a drown menu. In the user's case this can be applied to moving issues. The workaround would be too destructive as it would require the user to delete and remove the existing transitions and status and recreate them based on the required sorting needed.

        1. image-2017-09-20-22-32-08-588.png
          20 kB
          Niro
        2. step01.png
          20 kB
          Niro
        3. step02.png
          33 kB
          Niro

            Assignee:
            Unassigned
            Reporter:
            Niro (Inactive)
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: