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.
We have one project in our Jira cloud instance that is used by a handful of teams. This isn't convenient anymore so we are looking at creating new projects for some of these teams. My thought is that any of their tickets should be bulk moved over to the new project and then we can move the board(s) over as well.
Looking for confirmation and guidance to see if there is anything else we haven't thought of that would need to be done in order to not lose anything and make this a smooth transition.
@Paula Pokusa - You will want to make sure that you have the same issue types if that makes sense, workflows, screens, etc. If you are using the same processes for the team as you did on the old project. Most items you will be able to make changes and move if you miss them so it is not a big deal since the old project will still remain in your cloud instance.
To ensure that you do not lose issue data you will want to make sure that any custom fields are in place prior to the move so that data gets migrated. That is the only thing you can not make changes to after the move.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.