How to Migrate Issues Between Jira Projects While Retaining All Fields and Tabs?"

Tharunkumar B

I have a Jira project, Project A, which contains 15 issues. I need to copy or export/import these issues to another project, Project B. However, after migrating the issues, I’ve noticed that some fields and tabs are missing in Project B.

Example:

(Project A showing tabs and fields)

After the migration or copy, Project B has missing fields and tabs:

(Project B missing tabs and fields)

Steps Taken:

• Used CSV import to migrate issues.
• Attempted Bulk Copy Issue functionality.

Questions:

1. What is the best way to ensure that all fields and tabs are preserved when migrating issues between Jira projects?
2. Are there specific settings or configurations that need to be matched between the source and destination projects to avoid missing fields?
3. Should I manually recreate fields and tabs in Project B, or is there a more efficient method to synchronize them?

I would appreciate any guidance or suggestions to resolve this issue.

Thank you!

John Funk

Hi @Tharunkumar B 

When you migrate/move issues like that from one project to another, you need to take a few things in mind. If issues in Project A use Components, Releases, and/or Custom fields that have a Context just for Project A (or at least do not include Project B or are not Global), those items need to be setup in Project B before the migration. In other words, create the same Components exactly as well as the Releases. For the Custom fields, you need to update the Context to include Project B if the custom field is not global. 

Next, you need to review the screen schemes used by each project. If project A uses a screen with 3 tabs, but Project B does not. Then you either need to change Project B to use the same screen scheme as project A or modify the screen in Project B to add those tabs.  This can be done after the fact, and might be all that you need to do right now to see the fields from Project A within the Screens for Project B.