The /worklogs api seems to return worklogs sorted by started date. When trying to retrieve all the worklogs using this api, this sorting is error prone. We have more than 900k worklogs. Retrieving all of them using api takes a few hours (using offset and limit parameters). Should a worklog be deleted at the same time with a start date in the past, the offset parameter will no longer be correct and data will be missing. The result should be sorted by worklog id.
Guest
| Tempo Products | Tempo Timesheets |
| Tempo Platform | On-Premise |
Actually, the initial idea was not correct : it worked for added worklog but not for deleted worklogs.
Maybe the api should return results sorted by worklog id and limit and offset parameters (or equivalent) should apply to worklog id as well.
/worklogs?offset=0&limit=1000 would return worklog id from 0 to 1000 (number of results may be less than 1000).
/worklogs?offset=1000&limit=1000 would return worklog id from 1000 to 2000 and so on.
in that case, even if someone remove an old worklog, the api will always return the correct result.
Attachments Open full size