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.

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

            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2850542 ] New: JAC Bug Workflow v3 [ 2936527 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545265 ] New: JAC Bug Workflow v2 [ 2850542 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1551824 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545265 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 905418 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1551824 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow 20141014 [ 855302 ] New: JIRA Bug Workflow w Kanban v6 [ 905418 ]
            Martin (Inactive) made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            Martin (Inactive) made changes -
            Link New: This issue duplicates GHS-10725 [ GHS-10725 ]
            Oswaldo Hernandez (Inactive) made changes -
            Key Original: JRA-43041 New: GHS-11995
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 854742 ] New: GreenHopper Kanban Workflow 20141014 [ 854742 ]
            Project Original: JIRA [ 10240 ] New: JIRA Agile [ 12200 ]
            Jessica Riga made changes -
            Description Original: 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.
            New: 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.
            Jessica Riga created issue -

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

                Created:
                Updated:
                Resolved: