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

Move Issue fails to create change history items for values not in target field configuration scheme

XMLWordPrintable

      If you have two field configuration schemes, one with more fields, and you move an issue from the more fields scheme to the less fields scheme, the issue will no longer have values for the fields. This is OK and by design.

      However, what is also supposed to happen is that change history items should be created for all the fields that do not exist in the target field configuration scheme. The change history items should indicate the old value and the new (absent) value.

      If the issue being moved has subtasks and they also move field configuration schemes as a result of the also move subtasks option, these subtasks do get their proper change history items.

              mlassau Mark Lassau (Inactive)
              chris@atlassian.com Chris Mountford
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 11h
                  11h