-
Bug
-
Resolution: Fixed
-
High
-
4.4 - EAP, 4.4
-
None
-
4.4-beta1
4.4-rc1 still a problem
-
4.04
-
Setting/updating/getting values for multi-select field values prior to 4.4 used to be via values. Not it appears that ids are being used instead. This is a significant incompatibility. Here is the error:
com.atlassian.jira.rpc.exception.RemoteValidationException: Fields not valid for issue: Errors: {customfield_10041=Invalid value 's2' passed for customfield 'custom-multi-select'. Allowed values are: [s1, s2, s3, s4]}
- is caused by
-
JRASERVER-2983 Custom Fields: It should be possible to edit the options in a select list
- Closed
- is duplicated by
-
JRASERVER-25087 When using JIRA 4.4's SOAP API the values for Multi Select and Select List fields are incorrect
- Closed
- is related to
-
JRASERVER-25708 JIRA freezes creating issues
- Closed
-
JRASERVER-25732 Cascade select secondary value must be specified as an id
- Closed
-
JRASERVER-27269 SOAP getIssue - cascade select now returned as id instead of value on JIRA 5.0
- Closed
- relates to
-
JRASERVER-25374 Cannot update version custom field via SOAP on 4.4
- Closed
- was cloned as
-
JRASERVER-26707 SOAP progress issue fails with custom fields updates for select like field types
- Closed
- mentioned in
-
Page Loading...