Details
-
Bug
-
Resolution: Obsolete
-
Low
-
2
-
Severity 3 - Minor
-
Description
Summary
When JIRA and Tempo are installed, each worklog deleted is causing a huge number of entries, this is can be checked within the database, and is timing out the following API call, as the call has a limitations of 1000 results, which are easily passed by when this happen.
https://docs.atlassian.com/jira/REST/server/#api/2/worklog-getIdsOfWorklogsDeletedSince
Environment
(Optional - If Applicable)
- Cloud instance with Tempo Timesheets add-on installed
- Tested with a user with access to many projects
Steps to Reproduce
- Create an issue, with worklog
- Add some worklog entries
- Delete some worklog entries
- Perform the call from https://docs.atlassian.com/jira/REST/server/#api/2/worklog-getIdsOfWorklogsDeletedSince
Expected Results
Properly have each logwork delete entry shown in the call
The call is returning
Actual Results
We're still not able to isolate the quantization like X calls to 100X calls. But with a few deletes you easily timeout the call by exceeding the 1000 deletes limitation
Snapshot before the worklog was deleted:
select ( p.pkey || '-' || j.issuenum ) as issue_key, c.newvalue, c.oldvalue, g.author, g.created from changeitem c, changegroup g, jiraissue j, project p where c.groupid = g.id and g.created >= '2017-03-10 00:00:00.000+00' and g.created <= '2017-03-20 00:00:00.000+00' and c.field = 'WorklogId' and c.newvalue is null and g.author = 'sysadmin' and j.project = p.id; issue_key | newvalue | oldvalue | author | created -----------+----------+----------+--------+--------- (0 rows)
Notes
Snapshot before the worklog was deleted:
issue_key | newvalue | oldvalue | author | created -----------+----------+----------+--------+--------- (0 rows)
A snapshot from a select where a single worklog delete caused thousands of entries.
issue_key | newvalue | oldvalue | author | created ------------+----------+----------+----------+---------------------------- SFI-1 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 SD-12932 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 FSI-1 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 SDLC-12932 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 BPT-1 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 SDLC-12931 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 SOI-1 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 SD-12930 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 NHO-2 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 SDLC-12928 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 MGI-3 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 SD-12927 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 SFI-6 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 SD-12926 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 TME-10 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 SDLC-12926 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 IOPS-20 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 SD-12924 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 FBA-38 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 SDLC-12924 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 SOI-76 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 SDLC-12923 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 MGI-149 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 SD-12922 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 SDLC-312 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 SD-12920 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 SD-718 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 SDLC-12920 | | 203845 | sysadmin | 2017-03-21 14:58:46.895+00 ... (113012 rows)
Workaround
No workaround at the moment.
Attachments
Issue Links
- causes
-
-
- Closed
-
- cloned by
-
JCE-945 Loading...