Following the recent update (sometime in June 2017) to the Tempo Add on for use within the Jira platform, we noticed some strange behaviour when requesting to get the worklogs for a specific issue. When this request is made in the Jira API (api/2/issue/{issueIdOrKey}/worklog), the author and comment associated to the work log is always “Timesheets” and “time-tracking”. Further to our investigations, we discovered that the Tempo API can be used to fetch worklogs (rest/tempo-timesheets/3/worklogs) and the expected Authors and comments. Unfortunately, the logged times received are not whats being displayed in JIRA and we also are unable to see a way to connect/pair the JIRA worklog with the Tempo Worklog even if they have the same issue ID associated and have unique ID’s. We have also found another anomaly with receiving different number of work logs from the Jira API and the Tempo API, The numbers logged appear to to be coherent from eachs perspective since if we see 6 worklogs in the Worklog section of a Jira task, we get 6 from the API and if there are 17 entries in the Jira History section, Jira will also return 17 entries, but there is no real way to know which group to trust and since there is no way to associate a Jira Worklog with a Tempo worklog, it generates confusion when it comes to knowing the time actually logged in for a specific task. I have attached a sample of what we get for a specific worklog on each API for reference.