I have two issues with multiple subtasks, both are rendered oddly in the list view, and they aren't rendered the same way.

      The first one has 3 subtasks, and I can't find any way to get the parent issue to have the + on it so that I can collapse them in the list view.

      The second one has 11 subtasks. Upon first entering the list view, the parent issue always has the + on it. However, many (but not all) of the sub-tasks are exploded out.Once I expand and collapse it, everything appears fine.

            [JSWSERVER-757] Inconsistency in handling of subtasks in the list view

            JC added a comment -

            Hi Margaret,

            The initial problem comes from GHS-607
            Like this issue says GreenHopper is not handling the cloning, convert and move very well yet.

            The fix is stated in the issue but basically you just need to select all the misplaced sub-tasks above the parent and drag them on one of the subtasks below the parent.
            Your subs should all come back to normal.

            Let me know if worked out.

            Cheers,

            JC added a comment - Hi Margaret, The initial problem comes from GHS-607 Like this issue says GreenHopper is not handling the cloning, convert and move very well yet. The fix is stated in the issue but basically you just need to select all the misplaced sub-tasks above the parent and drag them on one of the subtasks below the parent. Your subs should all come back to normal. Let me know if worked out. Cheers,

            As you can see in the screenshot, ZPPS-1 has 3 sub-tasks, but no + on it. ZPPS-3 has 11, 9 of which are expanded as peers in the list.

            Martin Menu added a comment - As you can see in the screenshot, ZPPS-1 has 3 sub-tasks, but no + on it. ZPPS-3 has 11, 9 of which are expanded as peers in the list.

              jchuet JC
              4589295153da Martin Menu
              Affected customers:
              0 This affects my team
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: