-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
1
-
Minor
-
Steps to reproduce
- Create 2 projects in JIRA, PROJA and PROJB.
- Create a custom field of any type (tested with user picker field), and set the context to PROJB only
- Create an issue in PROJA
- Bulk move that issue to PROJB (notice that the custom field created earlier is required, even though it is clearly optional)
- Move that issue individually, without bulk move. (notice that the custom field created earlier is not required - Expected behavior)
Observation
Even though the field is flagged as required during the bulk move you can submit the form without inputting any values into the field (so technically, it is still optional, but the asterisk is misleading to users)
- duplicates
-
JRACLOUD-78440 Bulk moving issues to other projects shows non required fields as required and clear fields while moving
-
- Long Term Backlog
-
- relates to
-
JRASERVER-29250 Optional custom fields marked as required when performing a bulk move operation from one project to another
-
- Gathering Impact
-