nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

New Work Logs Not Accessible Via API After Creation

Ladislav Prchal

Hello,

I am trying to implement action-based script, that reacts on multiple actions in Jira. Whenever an action happens, webhook is fired with info to my app, where I do the rest of the action.

It works great for tickets (comments create/update, status update etc), however for work logs I have quite a problem.

Freshly created work logs are not accessible via API. At the same time, work logs which are there for some days are accessible without problem.

I could create my own "worklog" locally in my APP, however the data provided from webhook have Tempo Timesheet as the user.

How is this possible? Why work logs take so much time? How much time exactly? Is there a workaround?

Used API URL with baerer token... It works fine for this one for example. Higher number brings "worklog not found or you dont have access". Even though the work log was just created and I literally get the API URL to supposed worklog.

https://api.tempo.io/tempo-timesheets/4/worklogs/330013

Accepted answers

All comments

Susan Wu

Hi @Ladislav Prchal ,

If you are using Jira API to get Jira worklogs, then the worklog author is showing Tempo Timesheets as intended behaviour as Tempo hosts our own Tempo worklogs in different from Jira instance. Please refer to this KB for more details.

If you are using Tempo API to get worklogs, you will get the actual username as worklog author. However, you need to make sure you have either "View all worklogs" permission for all the projects or "View worklogs" permission for all Tempo Teams to view all worklogs. Else. you will only be able to view your own worklogs through UI and API with your bear token.

Hope this helps.

Best regards,

Susan Wu

Tempo Product Expert

Ladislav Prchal

Thank you for your reply, at this moment I think I found out the problem.

From webhook I retrieve JiraWorklogId, not TempoWorkLogId. Which is little bit not expected, but I think I am going to be able to get over it and post the whole solution.

As you can see here, when I list all worklogs in given ticket, I can see that in fact I do not have tempo ID.

So I need to find relation in between jira worklog ID and tempo worklog ID. I hope that I can get ticket key. If I have it, then I can just list all worklogs and get what I need.

And with the tempo worklog ID, I retrieve real data without tempo timesheet. It is pain, but ... yeah, it is pain...

Susan Wu

With Tempo API V3, you can see both jiraWorklogId and tempoWorklogId, but with Tempo API V4, you will only see tempoWorklogId. But you can still get jiraWorklogId with this endpoint on V4.

https://apidocs.tempo.io/#tag/Worklogs/operation/getJiraWorklogIdsByTempoWorklogIds

Ladislav Prchal

Excellent, thank you very much, going to test it on Monday, but this looks like exactly what I need. Have a great day!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

api

tempo