-
Bug
-
Resolution: Won't Fix
-
Low
-
15
-
Severity 3 - Minor
-
Summary
When the customer request to get worklogs using REST API calls, the application timeouts due to its performance.
In both cases, the users are trying to get deleted worklogs using this endpoint:
/rest/api/2/worklog/deleted?since=timestamp
However, in both cases, it's failing with HTTP/1.1 504 Gateway Time-out.
Our natural suspicion is that for both cases, there were too many worklogs retrieved, causing a timeout.
Environment
JIRA v1000.789.5
Steps to Reproduce
- Try to access this in a browser after logging in (or use curl to do a GET request):
https://example.atlassian.net/rest/api/2/worklog/deleted?since=timestamp - It will time out, give a Page Unavailable and add 504 - Gateway Timeout
Expected Results
The results must be displayed
Actual Results
The application timeouts
Workaround
None
- is caused by
-
JRACLOUD-66700 Multiple worklog delete entries for a single delete are registered when Tempo timesheets add-on is installed
- Closed
- was cloned as
-
JRASERVER-66180 JIRA Performance is bad to get deleted worklogs
- Gathering Impact