Copy Jira Board Into New Company Name Space

[MAKMCDO]

We have been working with an outside software developer for the last year and are now ready to bring development in house. We have done a lot of work setting up tickets in the contractors Jira space, but would like to do a bulk copy over to our own space. Assuming we have the cooperation of the contractor's Jira administrator, is this possible?

[Trudy Claspill]

Hello @MAKMCDO 

Welcome to the Atlassian community.

Is the other Jira system Jira Cloud or Jira Server/Data Center?

If it is Jira Cloud, is the project there Team Managed or Company Managed?

What information do you want to try to bring over? Do you want just the current issue state or are you hoping to get the issue history too?

Do you have agile boards, dashboards, and filters?

Do the users use the same accounts to access both systems?

[MAKMCDO]

1) The other system is Jira Cloud

2) Can you help me with the distinction between team and company? A groups of consultants form a team that have activity that I interact with on their board that lives in the consulting company's Jira instance.

3) Ideal scenario would be all the road mapping and feature description work that we have waiting in the backlog to be address.

4) Agile boards and Filters, we dont need the dashboards

5) I use the same set of credentials (Google) to get to both boards

Basically I want to copy this board and all associated stories/epics

[Trudy Claspill]

#2 - the project type is shown at the bottom of the navigation panel on the left. From your image, that says "team-managed".

There is a cloud-to-cloud migration tool that is currently in Beta release, but it does not support Team Managed projects per this documentation.

The same documentation talks about migrating projects from Cloud to a self-hosted Data Center instance and then to another Cloud instance. But again, Team Managed projects are not supported.

The last method in that documentation is to using a CSV export of the data and CSV import to add it to the destination system. This brings across only issue data, not boards or filters or roadmaps. Boards, Filters, and roadmaps would have to be recreated as would Workflows and custom fields. This method also doesn't bring across the history of the issues, so you would be getting only current state information.

CSV export doesn't require admin access on the source system. You use the Advanced Issue Search screen to get a list of all the issues you want and use the Export option on that same screen.

You would need to create the project on your system to receive the data, recreating the workflow and custom fields that are needed.

You may have to make changes in the exported data so that values for users and selection lists and statuses are an exact match for the values in your system.

Another limitation with CSV import specifically for Team Managed projects is you can connect child issues to Epics as part of the import process. That would have to be done manually after the import completes.

And another limitation is that you can import no more than 250 issues at one time with CSV import.

If you are interested in the CSV import option there are links to the Export and Import documentation in the article I referenced above. Here are some additional references.

1. In this post there is a screen image that shows the JSON format you can use if you want to try a JSON import of issue history. 
2. This article talks about the Created date for imported issues. By default the date will be set to the date you execute the import function.

[MAKMCDO]

So it sounds like my options are pretty limited.  Can we change the source board to "company managed" at this time or does that only happen at creation?

[MAKMCDO]

"Another limitation with CSV import specifically for Team Managed projects is you can connect child issues to Epics as part of the import process. That would have to be done manually after the import completes."

Did you mean to say "can NOT?

[Trudy Claspill]

You cannot flip a switch to change a project from Team Managed to Company Managed or vice versa. You have to create a new project and move the issues. Refer to this document for more details.

https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/

Yes, I did mean to say you cannot connect child issues to Epics during import to a Team Managed project.