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

Incorrect documentation article - Editing multiple issues at the same time

XMLWordPrintable

      Issue Summary

      The article outlines that:

      Standard issues can be moved to another project and issue type, whereas a sub-task can only have its issue type changed. (Note that it is possible to convert a sub-task to an issue, and vice versa.)

      However, sub-tasks can also be moved between projects.

      Steps to Reproduce

      1. Create two sub-tasks in a project.
      2. Using the Search for issues functionality, search for all of the sub-tasks associated with the project.
      3. Select the two newly created sub-tasks.
      4. Click on the Tools button and select Bulk change all 2 issues.
      5. Select the two issues and click on the Next button.
      6. Select the Move issues option.

      Expected Results

      • The procedure should not allow you to move the sub-tasks according to our documentation.

      Actual Results

      • The procedure is completed without any issues as we can see in the screenshot below:

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

        1. Screen Shot 2021-10-25 at 19.35.04.png
          Screen Shot 2021-10-25 at 19.35.04.png
          225 kB

          Form Name

            [JSWSERVER-21137] Incorrect documentation article - Editing multiple issues at the same time

            Oksana Levchuk made changes -
            Fix Version/s New: 8.16.0 [ 94593 ]
            Fix Version/s New: 8.17.0 [ 94802 ]
            Fix Version/s New: 8.17.1 [ 95400 ]
            Fix Version/s New: 8.18.0 [ 95094 ]
            Fix Version/s New: 8.19.0 [ 95693 ]
            Fix Version/s New: 8.21.0 [ 97590 ]
            Fix Version/s New: 8.22.0 [ 98792 ]
            Oksana Levchuk made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Closed [ 6 ]
            Oksana Levchuk made changes -
            Status Original: Gathering Impact [ 12072 ] New: In Progress [ 3 ]
            Oksana Levchuk made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 632639 ]
            Oksana Levchuk made changes -
            Remote Link New: This issue links to "Bugfixing process: JSWSERVER-21137 (Trello)" [ 632043 ]
            Oksana Levchuk made changes -
            Remote Link New: This issue links to "Bugfixing process: JRASERVER-44745 (Trello)" [ 619887 ]
            Oksana Levchuk made changes -
            Assignee New: Oksana Levchuk [ bc878d9874ad ]
            Tomasz Prus made changes -
            Status Original: Needs Triage [ 10030 ] New: Gathering Impact [ 12072 ]
            Bugfix Automation Bot made changes -
            Support reference count New: 1
            Gregory Peres (Inactive) made changes -
            Description Original: h3. Issue Summary
            The article outlines that:

            {quote}
            Standard issues can be moved to another project and issue type, whereas a sub-task can only have its issue type changed. (Note that it is possible to convert a sub-task to an issue, and vice versa.)
            {quote}

            However, sub-tasks can also be moved between projects.

            h3. Steps to Reproduce
             # Create two sub-tasks in a project.
             # Using the *Search for issues* functionality, search for all of the sub-tasks associated with the project.
             # Select the two newly created sub-tasks.
             # Click on the *Tools* button and select *Bulk change all 2 issues*.
             # Select the two issues* and click on the *Next* button.
             # Select the *Move issues* option.

            h3. Expected Results

            * The procedure should not allow you to move the sub-tasks according to our documentation.

            h3. Actual Results

            * The procedure is completed without any issues as we can see in the screenshot below:

             !Screen Shot 2021-10-25 at 19.35.04.png|thumbnail!

            h3. Workaround

             Currently, there is no known workaround for this behavior. A workaround will be added here when available             		New: h3. Issue Summary
            The article outlines that:

            {quote}
            Standard issues can be moved to another project and issue type, whereas a sub-task can only have its issue type changed. (Note that it is possible to convert a sub-task to an issue, and vice versa.)
            {quote}

            However, sub-tasks can also be moved between projects.

            h3. Steps to Reproduce
             # Create two sub-tasks in a project.
             # Using the *Search for issues* functionality, search for all of the sub-tasks associated with the project.
             # Select the two newly created sub-tasks.
             # Click on the *Tools* button and select *Bulk change all 2 issues*.
             # Select the *two issues* and click on the *Next* button.
             # Select the *Move issues* option.

            h3. Expected Results

            * The procedure should not allow you to move the sub-tasks according to our documentation.

            h3. Actual Results

            * The procedure is completed without any issues as we can see in the screenshot below:

             !Screen Shot 2021-10-25 at 19.35.04.png|thumbnail!

            h3. Workaround

             Currently, there is no known workaround for this behavior. A workaround will be added here when available

              bc878d9874ad Oksana Levchuk
              gperes@atlassian.com Gregory Peres (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: