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
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
Assume a company has 3 separate cloud sites. Also, assume their pockets are not deep enough for Atlassian Access and are not in a single organization in the Atlassian cloud.
Can they use tempo timesheets in all sites so that users who are common to multiple sites can log time and have a single master timesheet for management?
Hi @Rob Horan
I have used scriptrunner to pull tempo timesheet data for reporting to our HQ as csv
That process could be adapted to merge the data from 3 separate REST API calls.
I wrote that for a server instance using file system to create attachments. As part of our cloud migration I need to find an alternative approach.
That would allow to merge data from different instances, but you wouldn't have a single timesheet for approval, right?
I’m extracting data for upload to a separate external non-tempo timesheet system.
within Atlassian the sites would not be related to each other. With Access you could own the users consistently but that won’t unify the apps.
could you add application links and federate them as per server