-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
3.13
-
3.13
-
When you move an issue to another project, and that project has a Custom Field not available to the original project, then the user is prompted for a new value on the "Move Issue: Update Fields" page.
When they then move on to the "Move Issue: Confirm" page, it erroneously shows the new value as blank.
However, the new value really does end up in the DB.
- duplicates
-
JRASERVER-12479 OrderableField.getViewHTML on renderable customfields does not use passed issues value
- Closed
- is related to
-
JRASERVER-15823 Move Issue fails to create change history items for values not in target field configuration scheme
- Closed