We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

    • 1
    • 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.

      Atlassian Update: 3rd September 2019

      Hi everyone,

      In the new issue view you can now drag and drop subtasks in all issue detail view (board, backlog, full page, issue navigator). You can see the linked video in the attachments for how this works. Therefore, I am marking this issue as complete.

      The new issue view has been rolled out to all Jira Software cloud customers with the ability for each user to individually toggle it off or on. You need to have the new issue view toggled on to have this functionality.

      It should be noted however, that drag and drop for issues within an epic will not work. This is due to the fact that regular issue types - e.g. stories, bug, task - are tied into the global rank which can affect your backlog list. The subtask issue type(s) did not have this problem as they were not tied to the global rank. For example, if you moved the list of stories under an epic around, it would affect how those issues are represented in your backlog inadvertently and ways you may not have intended, causing confusion. We are designing the best experience for being able to drag and drop issues within an epic, while taking this into account. This will be shipped at some point in the future - no timeline yet unfortunately.

      I have created a separate issue to track that functionality specifically. https://jira.atlassian.com/browse/JRACLOUD-72887

      Regards,
      Taylor Pechacek
      tpechacek (at) atlassian (dot) com
      Product Manager, Jira Cloud

      Should be a way to move the subtasks up or down with a drag and drop feature instead of one row at a time. When there are an extensive amount of subtasks it is cumbersome and time consuming to move subtasks up or down one row at a time. Having a drag and drop feature would allow for quicker organization of the subtasks.

        1. subtask_DragandDrop.mov
          3.00 MB
          Taylor
        2. image-2016-09-07-12-08-18-491.png
          64 kB
          Kanstantsin Shautsou
        3. dragAndDrop_Subtask_issueView.mov
          8.81 MB
          Taylor

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

              • 1
              • 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.

                Atlassian Update: 3rd September 2019

                Hi everyone,

                In the new issue view you can now drag and drop subtasks in all issue detail view (board, backlog, full page, issue navigator). You can see the linked video in the attachments for how this works. Therefore, I am marking this issue as complete.

                The new issue view has been rolled out to all Jira Software cloud customers with the ability for each user to individually toggle it off or on. You need to have the new issue view toggled on to have this functionality.

                It should be noted however, that drag and drop for issues within an epic will not work. This is due to the fact that regular issue types - e.g. stories, bug, task - are tied into the global rank which can affect your backlog list. The subtask issue type(s) did not have this problem as they were not tied to the global rank. For example, if you moved the list of stories under an epic around, it would affect how those issues are represented in your backlog inadvertently and ways you may not have intended, causing confusion. We are designing the best experience for being able to drag and drop issues within an epic, while taking this into account. This will be shipped at some point in the future - no timeline yet unfortunately.

                I have created a separate issue to track that functionality specifically. https://jira.atlassian.com/browse/JRACLOUD-72887

                Regards,
                Taylor Pechacek
                tpechacek (at) atlassian (dot) com
                Product Manager, Jira Cloud

                Should be a way to move the subtasks up or down with a drag and drop feature instead of one row at a time. When there are an extensive amount of subtasks it is cumbersome and time consuming to move subtasks up or down one row at a time. Having a drag and drop feature would allow for quicker organization of the subtasks.

                  1. subtask_DragandDrop.mov
                    3.00 MB
                    Taylor
                  2. image-2016-09-07-12-08-18-491.png
                    64 kB
                    Kanstantsin Shautsou
                  3. dragAndDrop_Subtask_issueView.mov
                    8.81 MB
                    Taylor

                        Unassigned Unassigned
                        lnunes Leandro Fanese Nunes [Atlassian]
                        Votes:
                        227 Vote for this issue
                        Watchers:
                        109 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            lnunes Leandro Fanese Nunes [Atlassian]
                            Votes:
                            227 Vote for this issue
                            Watchers:
                            109 Start watching this issue

                              Created:
                              Updated:
                              Resolved: