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

Subtask ranking between board view and list in Parent issue disconnected

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Low Low (View bug fix roadmap)
    • None
    • None
    • None
    • None

      We have subtasks that need to be executed in a very particular order. The subtasks have been ordered correctly when looking at the parent issue, by using the up and down arrows. This does not seem to actually update their ranking though.

      When looking at the rapidboard view, the subtasks are not in the priority order they were put in under the parent issue. The board is ranking by rank. If I go back to the parent issue and use the gear to "rank to top" or "rank to bottom" then the order is updated on the rapidboard but not in the order on the parent issue.

      The two are disconnected from one another. You would have to manually rank them twice, using each ranking UI individually. Meaning that you would first go in and rank them all in the Parent Issue view. And then rank all of the sub tasks again on the board.

      I would expect the behavior to function basically the way updating ranking works when filtering by Epic on a backlog. You can update the relative order in just that epic. Then when you clear the filter the order of other issues has not changed. Meaning that if I update the ranking of subtasks on a parent issue, that is changing their relative order. So when looking at the Agile board, other issues may be sprinkled between them but the relative changes are reflected.

          Form Name

            [JSWSERVER-11995] Subtask ranking between board view and list in Parent issue disconnected

            Koby Wong added a comment -

            I'd love this feature as well. It's a minor inconvenience to have to re-rank the same subset of issues twice.

            Koby Wong added a comment - I'd love this feature as well. It's a minor inconvenience to have to re-rank the same subset of issues twice.

            Thanks for raising this issue, however it duplicates the existing linked issue.
            Please follow GHS-10725

            Kind regards,
            Martin
            JIRA Agile

            Martin (Inactive) added a comment - Thanks for raising this issue, however it duplicates the existing linked issue. Please follow GHS-10725 Kind regards, Martin JIRA Agile

            Oh no problem, I thought I'd add my two cents since your idea seems really rad.

            Steven F Behnke added a comment - Oh no problem, I thought I'd add my two cents since your idea seems really rad.

            Thanks @Steven!

            Jessica Riga added a comment - Thanks @Steven!

            I think this is more of an improvement than a bug, since we want the JIRA functionality to play ball with the JIRA Agile Add-on Functionality that is the ranking fields.

            I think that expecting the subtask reordering to affect ranking is crucial to interacting with the tool, the user experience is very disconnected without it.

            Steven F Behnke added a comment - I think this is more of an improvement than a bug, since we want the JIRA functionality to play ball with the JIRA Agile Add-on Functionality that is the ranking fields. I think that expecting the subtask reordering to affect ranking is crucial to interacting with the tool, the user experience is very disconnected without it.

              Unassigned Unassigned
              1ac9f9ea6c2b Jessica Riga
              Affected customers:
              1 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: