-
Bug
-
Resolution: Fixed
-
High
-
6.4.12
-
None
-
6.04
-
Was raised as part of a support ticket.
This seems to be caused because the EpicLinkCFType returns an IssueImpl object, which at the side of JIRA gets casted to a String (which throws an exception) (see TextCustomFieldOperationsHandler.getInitialValue()).
It's considered to be a TextCustomFieldOperationsHandler because of this check in CustomFieldImpl:
public RestFieldOperationsHandler getRestFieldOperation() { CustomFieldType customFieldType = getCustomFieldType(); if (customFieldType instanceof RestCustomFieldTypeOperations) { return ((RestCustomFieldTypeOperations) customFieldType).getRestFieldOperation(this); } return new TextCustomFieldOperationsHandler(this, getI18nHelper()); }
- causes
-
JSWSERVER-13429 Create issue from Confluence not working when linked to epic
- Closed
-
JSWSERVER-14623 Creating issue with epic link field through REST causes 500 Internal Error
- Closed
- is duplicated by
-
JSWSERVER-12506 Internal server error updating Epic Link field
- Closed
- relates to
-
JSWSERVER-7017 As a user, i want to add/update an issue Epic link by using REST API
- Closed
-
JSEV-212 Loading...
- mentioned in
-
Page Loading...