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.
Edit Nov. 6, 2020: Thank you for all your feedback. We’ve summarized and addressed your top concerns and questions on this thread. --- If you haven’t already read our recent announceme...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events