-
Bug
-
Resolution: Timed out
-
Low
-
4
-
Severity 3 - Minor
-
Summary
Creating an issue through REST API without setting required fields throws a misleading error.
Steps to Reproduce
- Set Description field to "required"
- run
curl -vvv -u email@email.com -k -X POST -H "Accept: application/json" -H "Content-Type: application/json" -d '{"fields": { "reporter":{ "name": "test" }, "issuetype":{ "name": "Cloud Support" }, "project":{ "key": "XXX" }, "summary": "Testing"} }' "https://instance.atlassian.net/rest/api/2/issue"
Expected Results
It should throw an error informing that Description field is required
Actual Results
It throws
{"errorMessages":[],"errors":{"summary":"Field 'summary' cannot be set. It is not on the appropriate screen, or unknown.","reporter":"Field 'reporter' cannot be set. It is not on the appropriate screen, or unknown."}}
Application logs:
Notes
Workaround
None
- is related to
-
JRASERVER-67013 REST API returns 400 error with misleading message when editing issues
- Gathering Impact
- relates to
-
JRASERVER-44003 HTTP 400 error with misleading information are returned when creating the issue through REST API as a user with insufficient permission or invalid Authorization header
- Gathering Impact