I have a csv backup of the previous Jira project that I'm trying to import into a new project. I'm finding it difficult to import it exactly as it is in my previous project with sprints broken down, status of tasks transferring and carrying over the descriptions. Basically, It's not coming over correctly.
Is there an easier way to transfer an exact copy of a project from one account to another?
Welcome to the community. If you want to move everything that is associated with a project from one instance to the other with CSV, this wouldn’t be possible. You should be able to move most insformation, however there could be things you’ll miss and it also requires creating fields and other settings manually.
The recommended way for what you intend is to:
Please note that at the moments the Jira cloud migration assistant doesn’t support Jira Service Management projects so if we are speaking of a service management project, you’ll need to migrate this with A CSV.
One other option which I haven’t tested in full would be using an add on like Exelate which allows data migration between 2 connected instances. This would require a lot of data mapping ahead of time though.
I hope this gives you an idea on what to do.
Hello @Alvaro Garibay
Welcome to the community.
If you want to get everything associated with the project (configuration, boards, etc) and keep all the original dates (creation date, etc), then what you need to do is go through a migration process. Unfortunately, there is not a native way to do this for a single project. Take a look at my response on this thread:
When you say "a csv backup" are you talking about the CSV output you can get from using the Export feature on the search screen? That might include Sprints to which the issues were assigned, but it doesn't include the Board where those sprints were created.
Was your source project a Company Managed project or a Team Managed project? It will say at the bottom of the navigation screen on the left.
If you are trying to import issue date extracted as a CSV from one project into another project, then the burden is on you to make sure that the configuration of that new project has already been set up to be identical to the source project. That would include setting up the workflow and creating custom fields.
I don't know that it is actually possible to "import" the association of an issue to a sprint with that method.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.