-
Bug
-
Resolution: Duplicate
-
Low
-
6
-
Severity 3 - Minor
-
Issue Summary
When trying to move an issue and its Sub-task from one project to another, it's requested to enter a value for a field that is NOT required in the target/origin project
Steps to Reproduce
- Create an Issue for a Project A
- Remove Project A from a specific Custom Field Context
- Perform a move on the issue from Project A to the Project B
Expected Results
The Move process should NOT require the custom field and the process should be completed.
Actual Results
The Custom Field from which Project A was removed from its context starts being requested.
Workaround
Add the Originating project to the Custom Field's Context and the move works without requiring the field.
You might also be able to complete the move operation without actually providing any values for the fields that are displayed as required.
- duplicates
-
JRACLOUD-78440 Bulk moving issues to other projects shows non required fields as required and clear fields while moving
-
- Long Term Backlog
-
- is duplicated by
-
JRACLOUD-77266 Optional custom fields are displayed to be populated during move operation
-
- Closed
-
- is related to
-
JRACLOUD-78440 Bulk moving issues to other projects shows non required fields as required and clear fields while moving
-
- Long Term Backlog
-