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
We love Insight, and we're thrilled to hear about Atlassian's purchase.
We have a lot of objects in our Insight Server that we want to import into Cloud.
However, when we try to do CSV import, Insight Cloud assigns a new key. This isn't feasible for our situation because we're not going to spend the a)time and b)money mailing out new asset tags for physical equipment, or ship/tag/return the physical equipment.
Are there any plans to address this paradigm?
Thanks for highlighting this and I've flagged up Key attribute consistency with the Insight product team.
We know that with the announcement about Jira Server that many people will be looking to do as you're doing and migrate. As we plan how Insight will be integrated into Jira Service Management we're considering all possible migration paths too.
Hi @Charlotte Nicolaou , thanks for your response.
I really hope this is something that can be accommodated.
It goes beyond the inconvenience of having to re-tag assets; many organizations set computer/server hostnames to the asset tag identifier, which has significant operational impacts if that has to be changed.
Hi @Andrey Suray we don't have a tool to help move data from Server to Cloud at this point. The suggested workaround is as follows:
We're looking at how we can make steps 1-3 easier by provide export/import of asset schema easier. Please feel free to contact our Migration Support team if you need further help.
Hi, thought it worth adding to this post for anyone else trying to use external system import to bulk update Insight fields during a cloud migration - the CSV field values for Insight custom fields need to be in the following format <WorkspaceID>:<ObjectKey>.
key, summary, insight
SANDBOX-2,this is my summary,dd4fe90e-752d-4103-8dad-abe7fd869b51:3
It isn't immediately clear from any documentation that this is the formatting required, the only thing I could find suggested that Label (Key) or Key should work but it doesn't. Note the : rather than a / which is what a CSV export chucks out at you.
Dear @Dylan , Is there any progress on the migration pathway for moving Insight Data from server to cloud ? We have an upcoming cloud migration where we need to move 2 Jira projects with extensive Insight usage. Since Insight is now natively available in JSM Premium cloud, will it be possible to have a similar integration possible where we have projects in Jira Software and Insight in JSM ?