You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Scenario summary: An On-Premise JSW server environment has an immediate need to add Time-sheets. Knowing the server is ear marked for migration, a cloud product/service to solve this new feature request is preferred over adding more server software & resources to the on-premise host. Duplicating project work, adding moving parts and complexity to the migration inventory, as well as potential feature differences.
Can Tempo Timesheets Cloud work with JSW server ?
Future proofing this feature add-on in the cloud ahead of the JSW server instance migrating.
Let us know ?
Just to clarify, you want to connect JSW server with Tempo Timesheets Cloud. Is that correct?
I’m not aware of this being a valid connection. My assumption would be that you would need a Jira Cloud instance to access Tempo Timesheets Cloud.
As you mentioned, you could use tempo timesheets on server though that brings with it issues with end of life support, and compatibility: https://help.tempo.io/cloud/en/tempo-server-migration-guide/server-data-center-vs--cloud--product-comparison/tempo-timesheets-server-data-center-vs--cloud.html
I would recommend moving to Tempo Timsheets Cloud AFTER your Atlassian migration is complete.
hope this helps,
Danny
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.