-
Bug
-
Resolution: Obsolete
-
Low
-
2
-
Severity 3 - Minor
-
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
Steps to reproduce
- Create 2 projects in JIRA, PROJA and PROJB.
- Create multiple Custom Fields, at lease a custom field 1 not required and Custom Field 2 Required,
- Set the context of any of the required custom fields to PROJB only (Not all have to have context set to PROJB and can have context set to other projects and destination project PROJA or global)
- Create an issue in PROJA
- Move Single issue to PROJB (notice that all custom field's created earlier are showing up on step 3 'Update Fields' of move even though Custom Field 1 is optional)
Documentation States:Custom Fields — If you have defined requiredcustom fields for your issue, which do not exist in your target project, you must set values for them. You will only be prompted to change the enter values for required custom fields in the target project, that are missing values. If you wish to change the existing values for other fields on your issue, you can do this after the move is complete.
And
If you are required to specify the values for any required custom fields (see explanation above), the Update Fields page is displayed. Specify the desired values for each field, and click Next to continue.
Expected Behavior
Only the Required Fields display on move at Update Field transition
- is related to
-
JRASERVER-39449 Optional custom fields are displayed on Update Field transition during move operation
-
- Gathering Impact
-