Tempo Ideas

Welcome to Tempo’s Idea Portal! Your suggestions are valuable to us and help us make our products even better.
Below is a list of ideas for Tempo, so please search, review and vote for those that would help you the most. We encourage you to add an idea if you don’t see it listed. You can stay updated on the work we are doing here at Tempo by contributing to this page.
To learn more and see our Frequently Asked Questions, click here.

Tempo and Jira show the same timestamp on worklogs

Tempo and Jira have different ways of calculating time zones and displaying worklog's timestamp. Would like to have them work the same way.

  • Richie Zhu
  • Dec 18 2020
  • Future consideration
Tempo Products Tempo Timesheets
Tempo Platform On-Premise
  • Attach files
  • Dmitry Balabka commented
    April 17, 2023 16:02

    I spent a time to find the exact explanation of the problem and finilly did. I just leave here a copy of my initial request to support team that explains the nature of the problem:

    I’m using “Log work“ to log my time. I noticed that the logged time appears in the wrong place on time table in "My Work -> Time view". It looks like the Time Log appears in “Central Daylight Time“ server time zone instead of my local “Europe/Riga“ time zone. (see the screenshot)

    Comments in Jira and other created objects appear at the correct timezone. So, I assume that Tempo incorrectly store or represent the creation time of the data.

    I read the Tempo Team explanation about this issue in the following:
    Why is there a time difference between my Jira worklog and my Tempo worklog?

    Unfortunately, the description proves that time for specific time zones is calculated incorrectly. A short explanation is available here:
    https://jira.atlassian.com/browse/JRASERVER-35503?focusedCommentId=1542134&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1542134

    The fact that “comments in Jira and other created objects appear at the correct timezone.” proves that you misuse timezones in the implementation.

    The following is another proof of the missused timezones:
    ”The user logging time is selecting a particular date and time for a reason. It is the day on which the work was completed. If that same user were to go to a country in another Time Zone, he would still expect his old worklog report to be the same as the day before he moved. (i.e., it makes more sense to him that this was logged at 8:00 AM wherever he was at that point in time, rather than having this recalculated to his current Time Zone, which would suggest that this was worked on at 10:00 PM on the prior day.)”

    If a person moves from timezone A to timezone B and wants to see work logs in timezone A using timezone B, it is impossible. A person simply should switch the timezone back to A (on his workstation). However, it is not always convenient, so it might be possible to specify the timezone direcly in Log Work form.

    Probably, the made mistake is complicated to fix:
    ”If we were to switch to Jira's model, all of our data would be inaccurate.”

    Still, it would be great if the solution will be found for at least new logs.