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; } } }

Tempo worklog startTime returning in author's timezone

Niels Frederiksen_1plab5

Hi, I am trying to update some fields on a tempo worklog via the API, but I want to avoid updating the startTime attribute.

From what I can gather, when I GET a worklog from the API, the startTime is in the author's timezone, but when update via PUT, then the request expects startTime to be in UTC.

That means that I can't just pass the startTime i get from the API, and I also can't just omit the startTime from the body, because for some reason it is then set to 0:00:00 UTC.

Do I really need to fetch the author's timezone and adjust the startTime accordingly to be able to update a worklog without changing the startTime?

Accepted answers

Tempo Support

Hi Neils,

You may want to explore the option of using Tempo REST API 4.0.

In this version the startTime is not required for updating a worklog. For more information please see the link https://apidocs.tempo.io/#tag/Worklogs/operation/updateWorklog

Best regards,
Chih from Tempo Support

All comments

Tempo Support

Hi Neils,

You may want to explore the option of using Tempo REST API 4.0.

In this version the startTime is not required for updating a worklog. For more information please see the link https://apidocs.tempo.io/#tag/Worklogs/operation/updateWorklog

Best regards,
Chih from Tempo Support

Niels Frederiksen_1plab5

Hi Chih, I am using the V4, but if I don't include startTime in the PUT request, then the time gets set to 0:00:00 UTC

Tempo Support

Hi Niels,

It is expected that the startTime of the worklog is defaulted to 0:00:00 UTC if you don't specify.

For the reason of this behavior, please see https://tempo-io.atlassian.net/wiki/spaces/KB/pages/232816644/Why+is+there+a+time+difference+between+my+Jira+worklog+and+my+Tempo+worklog

Best regards,
Chih from Tempo Support

Niels Frederiksen_1plab5

Hi Chih, thank you very much for this. This has helped a lot.

I can now see that my observed behaviour is only happening for worklogs that were created via Jira's API and not Tempo's. Worklogs created directly in Tempo work normally without timezone issues.

So I guess my next question is how can I identify which worklogs are from tempo and which were created in the Jira API. Is it enough to just check if the Author is the Tempo Timesheets add-on user when fetching the worklog from Jira's api?

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

tempo

tempo-timesheets

tempo-api