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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Currently we have Jira and JSM in a Data Center. We've built up an implementation of Insight whereby the objects are available on the JSM portal for the external customer to select when logging a new JSM ticket. We use the custom Insight Objects field in our JSM project and many of the internal development/engineering projects to display these objects and their attributes (e.g. instrument type, warranty type, warranty expiration, instrument status, etc...). Soon our IT dep't will move the JSM to the Cloud. Internal dev/engineering projects remain in Data Center. Because Insight is bundled with JSM, Insight moves to the cloud. Object management still possible in the JSM projects in the cloud. But we assume the Insight custom field and connection to the Insight data will be lost for our internal dev/eng projects. Wondering if anyone has worked around this problem before. Could we install a JSM in the Data Center just to use Insight in the Data Center and then somehow synchronize the Insight data between the Cloud and the Data Center Insight schemas? All ideas welcome.
How I would try and approach this:
From there it depends on how your dev/eng project use this data. Retaining the original Cloud object key would be key here (pun intended) to be able to link or sync in some way.
Hope this gets you started!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.