-
Suggestion
-
Resolution: Won't Fix
-
None
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
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.
- is related to
-
JRASERVER-15522 Fields not part of the destination form, should be STORED as a comment when moved/bulkmoved NOT lost.
- Closed
- relates to
-
JRASERVER-15823 Move Issue fails to create change history items for values not in target field configuration scheme
- Closed
-
JRACLOUD-14299 The treatment of subtasks of an issue that is moved is different between (single) Move and Bulk Move.
- Closed
- supersedes
-
JRASERVER-15716 Option to auto-assign all subtasks when moving moving a parent issue
- Closed
- was cloned as
-
JRASERVER-15522 Fields not part of the destination form, should be STORED as a comment when moved/bulkmoved NOT lost.
- Closed