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

The treatment of subtasks of an issue that is moved is different between (single) Move and Bulk Move.

    XMLWordPrintable

Details

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

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

      When I "MOVE" an Issue to a new project, you never get a screen asking for required changes to fields of that issues subtask.
      On the confirm page you get a warning:

      Note: Sub-Tasks associated with this issue will lose data stored in fields not applicable in the target.

      However, a Bulk Move operation works differently.
      We get a step in the wizard to ask the user to change values of fields that require adjusting.

      It would be nice if this was consistent.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-15522 Fields not part of the destination form, should be STORED as a comment when moved/bulkmoved NOT lost.

          • Low - Low priority issues
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-15823 Move Issue fails to create change history items for values not in target field configuration scheme

          • Medium - Medium priority issues
          • Closed

          Suggestion - JRACLOUD-14299 The treatment of subtasks of an issue that is moved is different between (single) Move and Bulk Move.

          • Closed
          supersedes

          Suggestion - JRASERVER-15716 Option to auto-assign all subtasks when moving moving a parent issue

          • Closed
          was cloned as

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-15522 Fields not part of the destination form, should be STORED as a comment when moved/bulkmoved NOT lost.

          • Low - Low priority issues
          • Closed

          Activity

            People

              Unassigned Unassigned
              mlassau Mark Lassau (Inactive)
              Votes:
              5 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: