-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
4.4.3, 5.0.7, 6.2.1, 6.2.7, 6.4.1, 7.3.6, 7.6.0
-
4.04
-
11
-
Severity 3 - Minor
-
0
-
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)
- is related to
-
JRACLOUD-80494 Optional custom fields marked as required when performing a bulk move operation from one project to another
-
- Closed
-
- relates to
-
JRASERVER-39449 Optional custom fields are displayed on Update Field transition during move operation
-
- Gathering Impact
-