Fields not part of the destination form, should be STORED as a comment when moved/bulkmoved NOT lost.

XMLWordPrintable

    • Type: Bug
    • Resolution: Handled by Support
    • Priority: Low
    • None
    • Affects Version/s: 3.12
    • Component/s: Bulk Operations
    • 3.12

      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.

            Assignee:
            Timothy Chin [Atlassian]
            Reporter:
            PaulC
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: