-
Bug
-
Resolution: Won't Fix
-
Medium
-
None
-
4.4.1
-
None
-
4.04
-
With the fix for JRA-25034 to make specifying custom field values consistently allow the user seen value (in addition to the value id), the secondary value for a cascade select is not handled. It must still be specified as an id. The returned value when retrieving the data is now returned in the user seen value .
- relates to
-
JRASERVER-25034 Multi-select custom field value handling incompatible with previous releases
- Closed
- was cloned as
-
JRASERVER-27269 SOAP getIssue - cascade select now returned as id instead of value on JIRA 5.0
- Closed