Asked to update custom fields that share the same settings among projects when moving issues where the field default value in the source project is configured for another issue type

XMLWordPrintable

    • 2
    • Severity 3 - Minor

      Issue Summary

      We are asked to update a custom field when moving any issue type from a project with a default value except for the issue type configured with the default value.

      When moving the issue configured with the default value, we are not asked to update the custom field with a default value.

      Steps to Reproduce

      1. Add to any custom field a default value for the Epic issue type in the source's project context.
      2. Create a Story issue type and move to the destination project as any type.

      Expected Results

      We should not be asked to update the custom field because it is empty in both source and target with no default value configured for the Story type.

      Actual Results

      We are asked to update the custom field.

      Workaround

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

            Assignee:
            Unassigned
            Reporter:
            Raf (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: