Unable to Retrieve Actual Worklog Author and Comment Using Jira REST API

Question

I am using the Jira API
/rest/api/3/issue/{issueIdOrKey}/worklog
to fetch all worklog details for a given issue.

However, I am facing an issue with the author and comment fields.
The author is coming as Tempo instead of the actual user who created the worklog, and the comment value is always something like "time tracking" instead of the comment entered by the user.

I do not want to integrate Tempo into my project.
I only want to use Jira APIs and retrieve the actual author and the original comment entered at the time of logging work.

I am integrating Jira APIs into my organization’s project.
Please let me know if there is any way to get the correct author and comment details using Jira APIs only.

Natalia_Kovalchuk_SaaSJet_ · Answer

Hi @Bittu Kumar !

In case the time was logged via Tempo, Jira saves the worklog as created by the Tempo app user, not the real person. The real name of the author and the original comment are stored inside Tempo, not in Jira. That is the problem.

So when you call:
GET /rest/api/3/issue/{issueIdOrKey}/worklog

Jira can only return:

Author → Tempo (app user).

Comment → generic text like “time tracking”.

So, if the worklog was created by Tempo, Jira doesn't have the actual author or the original comment. In such a case, you can try to use the Tempo API.

If you need to export all work item history with comments in Excel or CSV formats, you can also try Issue History for Jira app from SaaSJet team.

Hope this will be helpful!

Marc -Devoteam- · Answer

Hi @Bittu Kumar

So it seems you are using Tempo for time writing instead of the ootb time Writing option.

This is why the Jira API shows the worklog author as Tempo.

Use the Tempo api to get the author of the worklog.

Deniz Oğuz - The Starware · Answer

Hi @Bittu Kumar

Unfortunately this is a design decision of Tempo app. They don't store actual user and comment information on the worklog itself. This is why you are getting a placeholder author and comment. They are storing them on their own backend. This has some advantages and some disadvantages as you have experienced.

We have prepared a migration guide for helping people migrating from Tempo to WorklogPRO in our wiki. You may want to check it. You may apply a similar solution.

Regard,

Deniz