Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-8053

Reorganize sub-task order within the parent task

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Currently, sub-tasks are ordered in the parent view by creation time, and can be moved up or down in the list by clicking on the arrows. When lists of sub-tasks becomes long, it is quite tedious to reorganize, especially when adding new higher priority sub-tasks (they start at the bottom of the list).

      It would be nice to have a feature that allows sub-tasks to be inserted at a desired position in the list, and possibly a number of sub-tasks to be moved/inserted as a bulk operation.

            [JRACLOUD-8053] Reorganize sub-task order within the parent task

            Tair Tidhar made changes -
            Component/s Original: Issue - Navigation [ 46635 ]
            Tair Tidhar made changes -
            Component/s New: Issue - Search - Frontend only [ 77950 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3153353 ] New: JAC Suggestion Workflow 3 [ 3643762 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2337445 ] New: JAC Suggestion Workflow [ 3153353 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Eric S (Inactive) made changes -
            Component/s New: Issue Navigation [ 46635 ]
            Component/s Original: Issue Navigation & Search - Bulk Operations [ 46560 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2101928 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2337445 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2064403 ] New: JIRA Bug Workflow w Kanban v6 [ 2101928 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 1869162 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2064403 ]
            jonah (Inactive) made changes -
            Description Original: Currently, sub-tasks are ordered in the parent view by creation time, and can be moved up or down in the list by clicking on the arrows. When lists of sub-tasks becomes long, it is quite tedious to reorganize, especially when adding new higher priority sub-tasks (they start at the bottom of the list).

            It would be nice to have a feature that allows sub-tasks to be inserted at a desired position in the list, and possibly a number of sub-tasks to be moved/inserted as a bulk operation.
            		 New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-8053].
              {panel}

            Currently, sub-tasks are ordered in the parent view by creation time, and can be moved up or down in the list by clicking on the arrows. When lists of sub-tasks becomes long, it is quite tedious to reorganize, especially when adding new higher priority sub-tasks (they start at the bottom of the list).

            It would be nice to have a feature that allows sub-tasks to be inserted at a desired position in the list, and possibly a number of sub-tasks to be moved/inserted as a bulk operation.
            jonah (Inactive) made changes -
            Link New: This issue is related to JRASERVER-8053 [ JRASERVER-8053 ]

              Unassigned Unassigned
              5cda7d3b902b Adriano Bertucci
              Votes:
              74 Vote for this issue
              Watchers:
              28 Start watching this issue

                Created:
                Updated:
                Resolved: