Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-17312

The "Move" operation may produce subtasks with invalid empty values in target project

    XMLWordPrintable

Details

    Description

      When moving an issue with sub-tasks between projects, we need to move the sub-tasks. Sometimes the fields of the moving issues need to change to fit into the target project. The "Move" operation presents a mapping GUI for the parent issue when this needs to occur. It does not have a GUI for sub-tasks remapping. To move the sub-tasks it simply fills in the default value for fields that must change. For example, when moving a sub-task between projects its components field will be cleared. This can leave the sub-tasks in invalid states. For example, a moved sub-task will be invalid in a target project with compulsory components.

      This is a problem for at least the Component and Due Date field.

      The simplest solution would be to use the "Bulk Move" operation to perform a "Move". The bulk move has the step to configure the sub-task mappings that the regular move does not. All that would be required would be to hide the fact that we are doing a bulk move while performing a logical "Move".

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. JSWSERVER-11255 Move issues between projects not working using Jira Agile board if the issue have subtasks

          • Medium - Medium priority issues
          • Closed
          has a derivative of

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-31734 NPE error when moving issue with subtask in case target project has a different workflow for the subtask

          • High - High priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-27346 sub-task workflow is wrong during move of parent

          • Medium - Medium priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-29630 Sub-Tasks Not Using Assigned Workflow When Moving Parent Issue To Another Project

          • Medium - Medium priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-31022 Moving a subtask with its parent does not validate the custom field context

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-37722 Unable to move issue with sub-issues to another project with different workflow

          • Low - Low priority issues
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-13011 Component of a subtask is still component of original project after moving an issue

          • High - High priority issues
          • Closed

          Activity

            People

              natashbar Norman Atashbar
              bbain bain
              Votes:
              9 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: