Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Handling of existing work logs after installing/uninstalling Tempo Timesheets

Hi Community,

in the course of evaluating Tempo Timesheets (for Jira Server) we need to have a clear understanding on the following:

We understand that Tempo work logs are stored in a proprietary Tempo database, syncing work logs to the Jira data base (Time Spent). 

  • what happens with existing work logs in Jira (time spent) after installing Tempo? Assuming to have the respective Tempo permissions, the existing work logs (Jira Time Spent) before installing Tempo are not deleted and will be processed also by Tempo Reports in addition to Tempo work logs, right?
  • what would happen with Tempo work logs, if Tempo would not be used anymore and uninstalled from a Jira Server instance? Tempo Work Logs would still be shown in Jira Time Spent fields, right?

Thanks for your response and sharing your valuable experience

2 answers

Hi @René Hans and @lizhonghua ,

On Server, all worklogs are stored in the JIRA worklog table, independent if they were created via the native JIRA log work dialog or the Tempo Log Time dialog.

In Tempo, users can always view their own worklogs in My work or the Tempo Reports. To view worklogs of other users, permission to do so needs to be given.

Please take a look at for more information

Best regards,
Susanne Götz
Tempo team

hi @Susanne Götz _Tempo_ ,

Thanks, we have serveral projects under the same account, is there way to make some of projects view/create worklogs via JIRA native page but other via Tempo log time page? thanks again.

Hi @lizhonghua ,

It is not possible to allow /restrict users to log work via Tempo only on specific projects when users have the "Work on issue" permission. 
The Tempo installation is global and the option to log work is available in all issues that the users are allowed to log work on.

Worklogs will be displayed in Tempo (depending on the viewers permissions) independent if they were created in JIRA or in Tempo.

Best regards

hi, @Susanne Götz _Tempo_ 

thanks so much, very helpful to me.

My case is party of our department members had records worklogs via JIRA native page. we are trying to use Tempo timesheet, but these worklogs disappeared after Tempo installation, do you have any suggestion on how to migrate the exsiting worklogs to new view smoothly? on the other hand, can they continue to work on the worklogs via jira worklogs page with the existing data after we decide to uninstall the Tempo add-on? 

Thank you so much.

Hi @lizhonghua 

there is no need to migrate the worklogs. 

Users should be able to see their own worklogs when they go to Tempo, My Work.

To view worklogs of other users, they need to have the
- "View all worklogs" permission for the JIRA projects that the other users have logged work on (this permission is set in he JIRA project permissions, or the
- "View team worklogs" permission for the team(s) the other users are members of  (

They can then view the worklogs in the Tempo, Reports view (

Best regards,

hi, @Susanne Götz _Tempo_ 

Could you please check whether I understand correctly. does that means the existing worklogs created via native can be viewed in Tempo report pannel after configurate the neccesarry permission, and we can use Tempo intead of native page to record the new worklogs. both the exsiting worklogs(created by native page) and new worklogs (created by Tempo) can be listed in Tempo's reports pannel. 

thanks so much. 

Hi @lizhonghua ,

Yes, this is correct.

Best regards,

I have the same question but for Jira Cloud - if we uninstall Tempo, can we still see the worklogs?

we met the same case that the existing worklogs disappeared after the Tempo timesheet installation. is there any advice on how to make them work again. any comment would be much appreciated. 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events