Transfer Project

[Neil Magill]

Hi Jira community, the company i work for is currently in the process of separating, which means we will have two instances of Jira, one for each side. 

There are several projects with Tasks, Issues, Bugs, epics etc that i need to copy to the other instance of Jira (new company) 

I have tried the normal way by going into the filters and exporting all the tickets for each project one by one and then trying to import them into the specific project they are required.

But when i add the CSV and try and map the fields, i am getting 100s of errors when i validate before import? 

I am being soft or is there an easy way to do this? If there is a way for me to contact an atlassian agent ill do that too.

Thanks in advance. 

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

Hard to say without knowing what the errors are.  What type of import are you doing?  A project one, or an admin one?  (Project imports need you to set up the projects with all the fields before they can run, admin ones have options to create and populate fields automatically)

[Neil Magill]

Hi Nic,

I am doing a CSV import.

So i exported from Jira 1 from project 1 and i then log into Jira 2 and try and import into project 1. Below are the issues

[Nic Brough -Adaptavist-]

We have no access to your system to see the logs.  Which import are you using (admin or project) and what do the logs say the 4 warnings and 182 errors are? 

I'm guessing they are all related - the 182 error lines are likely to be saying two or three similar things like "field X doesn't exist for issues 4, 17, 28, 46 etc

[Neil Magill]

Do you have a contact number i can call you on to discuss?

[Nic Brough -Adaptavist-]

Ok, most of those are pretty clear

• The issue type [ [System] Change ] does not exist or it's not applicable for the selected project. The affected issues will be created with issue type [ Story ]
  • You have not mapped your issue type in the CSV to an issue type that exists in the project, it's defaulting to Story so you get your issues in.

• Issue can't be created due to the error/s [ Epic Name is required. ]
  • You can not leave Epic name blank on Epic.  You will need to add it into your CSV as another field.  (A lot of us just copy the summary column)
• Subtask 'Bug: behaviour of YES/NO buttons on Module Completion screen is inverted' doesn't have a valid Parent Id selection. Issue will not be created.
  • This is a cascading select list, and your CSV does not contain valid data for it.  Either remove the column or mapping, or add valid data for it
  • This applies for all the rest of the fields - the "parent id" is the top level value in a cascading select, and you're only mapping the lower level