-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Highest
-
None
-
Affects Version/s: 3.0.2
-
Component/s: Issue - Fields
-
Environment:
3.0.2-#74
-
3
We have just experienced very strange behavior.
A child option was being added to a custom cascading select, and all child options now appear under a different parent on the edit issue page.
Note that on the ‘Edit Custom Field Options’ page, ironically all of the fields are appropriately aligned with the parent option.
At the same time, a custom user field was marked as required, now all the data is not appearing.
Please help, this is a huge problem.
- relates to
-
JRASERVER-5010 "None" is still selectable in a cascading select custom field despite being set to required
-
- Closed
-