-
Bug
-
Resolution: Timed out
-
Low
-
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
- Add to any custom field a default value for the Epic issue type in the source's project context.
- 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
- relates to
-
JRACLOUD-79050 Moving issues between projects with different field configurations causes fields to pop up in "update fields" if using different renderers
-
- Closed
-
-
JRACLOUD-78440 Bulk moving issues to other projects shows non required fields as required and clear fields while moving
-
- Long Term Backlog
-