Best Practices for moving issues to a new project Edited

[hellok]

Looking for best practices for moving issues to a new project

Basically move all the issues from project A to Project B and retire A.

Please throw in some ideas.

Can we take individual backup of each project?  How to do that? 

[William Naughton]

Hi,

Is the bulk update not available in Jira Cloud? For Jira Server in the Issues module you switch to the View all issues and filters view, you can select all the issues then and do a Bulk change which includes moving issues to another project.  If you have some fields populated like Component, Fixed Version, it will ask you to choose a value if it does not already exist in the new project.  You can choose to leave it blank.

We had to do this when we merged a couple of projects into one project.  Note, the issue key (id) will change in the new project.  You can still search for the old id and it will bring you to the new issue.  Pretty cool.

Bill

[hellok]

Yes Bill. Bulk move is available and we will be using that. 

But I would like to know the checks we need to take care of like 

1) taking backup of the issues (something like a RESTAPI ) without using the Admin permissions

2) how to configure the boards 

3) what to do for bitbucket integration

4) How to deal with Roadmaps

5) how to filter by different teams in the new project.  Is it better to create a new Teams field or anything else that can be done to see the segregation of issues by different teams even after merger