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
Been asked by my leadership to take point on our cloud migration. I have some outstanding questions from my leadership that I'm having difficulty finding answers on. Maybe you all can help me out
Current outstanding questions:
-Can we migrate data from a subset of projects or spaces?
-Does the migration keep the existing Jira card number, e.g., IRP-31?
-Ability for links within Confluence and Jira to function as expected after migration, e.g., links to Jira, links to Confluence, links to external Google docs?
-Can backlog items be flagged to not get migrated?
-Does Easy Agile add-on data migrate to the Cloud?
Let me see if I can answer these questions for you.
Hi @Brian Golden - I would recommend you to be in touch with a solution partner to help you with a smooth migration to cloud. You will also get detailed and contextual responses to your queries.
@Brian Golden , somewhat uncertain on answers, but these are some of the same questions we're looking at as well in weighing a potential future migration. My understanding (which I'd love to hear from others if I'm wrong on) goes like this:
1) Subset migration. There's an answer on this I see already posted, but you should consider carefully what problem you're trying to solve here. Are you intending to have a transitionary period where your company is split on DC and Cloud?
2 & 3) On the "problem you're trying to solve" I'm guessing you're thinking of continuity support for incoming links. From our discussions with Atlassian (which I hear second hand at this point) it sounds like Atlassian can provide a mapping of old to new. Our theory right now is that we can make the redirect facility to provide that continuity, but my understanding is that this is from our IT group, not Atlassian-provided. You may want to check in on your local resourcing.
4) I get the impression that the idea is that if you don't want to migrate something, then clean it up ahead of migration. That would be deletion in this case, as you might have read about the problems Atlassian currently has with migrating Archived items.
5) Talk to the add-on vendor.