-
Bug
-
Resolution: Fixed
-
High
-
9
-
Severity 3 - Minor
-
7
-
Issue Summary
Creating or updating a high number of issues via the /rest/api/3/issue/bulk endpoint leads to 404 errors.
Steps to Reproduce
- Use the /rest/api/3/issue/bulk endpoint to create/update a significant amount of issues
Expected Results
The request completes and a 2XX status code is returned.
Actual Results
The request fails with a 404 status code.
Notes
While it is true that the request returns a 404, all the issues will be correctly created.
This has been reproduced when creating/updating over 200 issues, but depending on the Jira configuration it could occur with a smaller payload.
This problem occurs for the following reason:
- the /rest/api/3/issue/bulk request is being processed in a synchronous way
- when the request payload contains a high number of issues to be created (e.g. 200), this leads to a 404 http status code being returned
- even if the app requesting the endpoint receives a 404, all issues are created by Jira
When using the second version of the api /rest/api/2/issue/bulk the error returns as HTTP 504.
Workaround
Reducing the number of issues updated or created will prevent this issue from occurring.
- relates to
-
JRACLOUD-67623 It would be nice to have REST requests to the rest/api/2/issue/bulk endpoint handled asynchronously so that they don't hit the proxy timeout of 60 seconds.
- Closed
- has action
-
ISSUE-4403 Loading...