Importing Issues

[Ann Dunn]

How do I import existing issues on a project to a new project? I need to duplicate the project. I have exported the issues into a CSV file. However, there are some fields that should not be carried over. What are those fields?  Once I get all this done, how do I import this data into the new project? 

Also, is there a better way to duplicate a project?

Thanks!

[Jack Brickey · Accepted solution]

hi Ann,

have you seen this article? create-issues-using-the-csv-importer 

[Trudy Claspill]

Hello @Ann Dunn 

When you say you want to duplicate the project, what problem are you trying to solve? Are you trying to make an exact copy that includes the history, comments, and all links in the current issues? Or are you trying to create a new project with a set of "new" issues at the beginning of their lifecycle with no history?

You said there are some fields that should not be carried over, but then asked us which ones those would be. We can't determine that for you. It is up to you to decide what data you want to migrate for each issue.

Is your source project a Team Managed project or a Company Managed project? And what about the destination project? This can impact the import process.

Are you a Jira Administrator? This can also impact the import process.

With answers to the above we can provide better guidance to you.

[Ann Dunn]

Hi Trudy. You're correct. What I meant to say is that some fields, like index, should not be imported into the new project. Are there any such fields that I may need to blank out on my CSV file? I need to duplicate a project to give me an area to test new parameters without changing the existing project. I'm new to the project/team and need to explore some new ideas. Both source and destination projects are Company Managed projects.

I have been made a Jira Admin, but this seems to 'come and go'! WE don't understand why that's happening. 

Thanks!

[Trudy Claspill]

You don't need to "blank" columns out in your CSV file. Simply do not map them to fields when you come to that mapping step in the import process.

The data you might need for "testing new parameters" depends greatly on what changes you are trying to test.

The CSV import process doesn't support importing issue history.

You have to execute the import as a Jira Admin from the External System Import page if you want to import issues with any status other than the one they would be set to when an issue is newly created, I believe, as it used to be that importing through the Search Issues page would only set them to that first status.

Do you want to retain issue links, if they exist, to the original issues, or recreate those same links but only between the newly created issues when you are importing the data?

Do you want to mirror the Epic/Child Issue relationships in the issues created by the import?

Do you want the users associated with the original issues to be associated to the new issues? Do you want them to receive notifications about changes in those new issues?

Your new project will have to be set up with the same schemes as your source project initially to support the import, but then if some of the changes you want to test involve changing those schemes, you'll have to make copies of those schemes for testing so that your source project isn't affected.

[Mikael Sandberg]

Hi @Ann Dunn,

Welcome to Atlassian Community!

You can use the bulk import feature to do this, just link the fields you want to import into the new project. Have a look at Import data from a CSV file for more information.