-
Suggestion
-
Resolution: Won't Do
-
None
-
None
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Summary:
Please improve JIRA so that when moving an issue from one project to another, if there is a custom field with different contexts for each project it will retain that value. Currently it does not.
Steps to Reproduce:
- Create Custom Field with different contexts for Project A & Project B (as in the attached screenshot).
- Create Issue in Project A with one value in the Custom Field.
- Bulk Move the issue to Project B.
- Select the retain check box and complete the move.
Expected Results:
The value would be retained.
Actual Results:
The value is not retained.
Notes:
This happens for both move and bulk move, however move never offers the retain option. It is possible that the context for the target project will not have the same options as the source project - I'm unsure how to suggest best handling of this.
- relates to
-
JRACLOUD-31021 Retain values for a custom field with different contexts when moving the issue
- Closed
- Testing discovered
-
JRASERVER-31022 Moving a subtask with its parent does not validate the custom field context
- Closed
- mentioned in
-
Page Loading...