Details
-
Bug
-
Resolution: Fixed
-
Low
-
None
-
1
-
Severity 3 - Minor
-
Description
Summary
When trying to create an epic via REST API v3, for example:
curl --request POST \ --url 'https://<instance>..atlassian.net/rest/api/3/issue' \ --header 'Authorization: Bearer <access_token>' \ --header 'Accept: application/json' \ --header 'Content-Type: application/json' \ --data '{
It returns
{
"errorMessages": [],
"errors":
{ "customfield_10010": "Operation value must be an object" }
}
customfield_10010 is Epic Name. Upon checking the datatype for Epic Name, it seems to be String but it's still throwing out the error.
Environment
- REST API v3
Steps to Reproduce
- Create an EPIC via REST API v3
Expected Results
Epic is created
Actual Results
{
"errorMessages": [],
"errors":
{ "customfield_10010": "Operation value must be an object" }
}
Workaround
Run in REST API v2. For example:
curl --request POST \ --url 'https://<instance>..atlassian.net/rest/api/2/issue' \ --header 'Authorization: Bearer <access_token>' \ --header 'Accept: application/json' \ --header 'Content-Type: application/json' \ --data '{