-
Bug
-
Resolution: Duplicate
-
Low
-
6
-
Minor
-
0
-
Issue Summary
Optional custom fields are displayed to be populated during move operation
Steps to Reproduce
1. Create 2 custom fields (For example Single text field 1 and Single text field 2)
2. Create context for both fields such that the fields have the scope set to "Bug" issue type and all projects (Global)
3. Create a Jira project and create different screens for Story and Bug issue types.
4. Add the 2 fields to the Bug screen only in the above created Jira project.
5. In the project field configuration, mark "Single text field 1" as "Required" while "Single text field 2" is optional.
6. Create a story issue in the project and move the issue from Story to Bug.
Note: Even though 2 fields are added to a single project screen, the field appears to be populated during the Move operation to bug issue type in multiple projects (even though the field is not added to the bug screen configuration in that project)
Expected Results
During the move operation, only the "Single text field 1" field should be prompted to be populated as it is a mandatory field.
Actual Results
We notice that both "Single text field 1" (Required) and "Single text field 2" (Optional) are displayed to be populated during the Move operation.
Workaround
It is possible to continue with the move operation by only populating the mandatory fields. Not populating the optional fields would not affect the move operation.
- duplicates
-
JRACLOUD-78048 When moving an issue to another project or issue type, if the originating project/issue type isn't part of the custom field's context, the CF is presented as a required field
-
- Closed
-
-
JRACLOUD-78440 Bulk moving issues to other projects shows non required fields as required and clear fields while moving
-
- Long Term Backlog
-