Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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
4,467,284
Community Members
 
Community Events
177
Community Groups

Is it possible to migrate WorklogPro data to Tempo Timesheets? (Server to Cloud)

Rob Horan Community Leader Feb 02, 2022

I am working with a team that is looking to migrate to the cloud and would like to migrate WorklogPro data to Tempo Timesheets.  They use a WorklogPro field to categorize their work.  Is it possible to migrate this data, including work category, to Tempo, using worklog attributes?

1 answer

1 accepted

1 vote
Answer accepted
Rob Horan Community Leader Nov 03, 2022

So here's how it all worked out. 

Our customer selected Tempo Timesheets, given that it is widely recognized as the best-in-breed choice for timesheets in Jira.

Once installed, Tempo Timesheets was configured according to the app documentation.

The customer then used Tempo's bulk edit feature to migrate their WorkLog Pro category values to Tempo Accounts. See https://help.tempo.io/cloud/en/tempo-timesheets/setting-up-and-configuring-tempo-timesheets/bulk-deleting-and-moving-worklogs/editing-time-records-in-bulk.html

For reference, we also encountered a bug that displayed an "Issue not found" error when trying to log time. This error results from a known bug that affects the cloud version of Tempo Timesheets. See https://tempo-io.atlassian.net/wiki/spaces/KB/pages/204898357/Why+do+I+receive+Issue+not+found+error+when+trying+to+log+time for more details.

 

Solution:

The "atlassian-addons-admins" group needs to have the "Browse users and groups" permission in Jira Settings, System, Global permissions so that plugins can check the permissions a user has in JIRA.

 

It may be that the Tempo add-on (Tempo system user) is lacking the Browse Projects permission for the issue's project. This permission is required for apps like Tempo to access issues and function correctly.
Please follow these steps to ensure that this is set correctly: 

  1. Navigate to Jira Settings > Issues > Permission Schemes;
  2. Add the atlassian-addons-project-access  Role to all Project permissions in all Permission schemes that are used in your Jira instance.
  3. Verify if you can now log time on the issue (note that this might take some time to take effect)

We also worked with Tempo Support to address an issue on the back end, which prevented historical work log information from appearing in Time Logged reports.

Tempo's support team was incredibly helpful throughout this migration, and their efforts were truly appreciated! 

That's great to hear, @Rob Horan  😎

Thanks for sharing.

Like Rob Horan likes this
carolyn french Community Leader Nov 03, 2022

Hi @Rob Horan I passed along your message to our Support team and they are thrilled to have helped.

Thank you for following up with your post to let others in the Community know how you executed this migration for your customer and set up Tempo, including using our new Cloud feature Bulk Edit! 

Carolyn

Tempo Customer Success

Like Rob Horan likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events