nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Seamless Jira tickets migration from team-managed project to a company-managed project

Mavi_azjump

HI, could anyone help me please? I am trying to set a new board (company-managed project), I have configured the fields. Now, my next step is to migrate the jira tickets from the old board (team-managed project) to the newly created one. I configured the fields and have chosen the active fields from the old.

I did some test by cloning 1 ticket to move to the new board. However, some details were not copied. There are missing details.

What is the best and seamless way to move the tickets to the new board without worrying if I missed some details or not.?

Accepted answers

All comments

Pramodh M

Hi @Mavi

Moving the issues is the best way to migrate the issues from team managed project to company managed project

As you have a premium version, you could test the move feature in a sandbox environment and observe the changes in a company managed project.

We had earlier done the same and it retained all the fields without any loss.

Thanks,

Pramodh

John Funk

Hi Marivi,

Can you be more specific about which details were missing?

Luka Hummel - codefortynine

Hi @Mavi

While Jira's native tools can handle most basic migrations, for more complex scenarios or to ensure a more seamless, you could try using a third-party app like our Deep Clone for Jira. Deep Clone allows you to bulk clone and move multiple issues between projects while maintaining all details, including comments, attachments, and even links between issues. It's particularly useful if you find the native Jira migration tools lacking in flexibility or functionality.

Mavi_azjump

Hi, thanks for your reply. I actually did the 'move' but it did not copy the customized fields.

Mavi_azjump

would it include custom fields?

Mavi_azjump

the custom fields created in the team-managed project, even if I recreated the custom fields in the company-managed project, still they were not copied.

Luka Hummel - codefortynine

Deep Clone does clone custom field values between team-managed and company-managed projects if there is a custom field with the same name (including capitalization) configured in both projects.

John Funk

Maybe there was a problem at the time, but if you create the Custom fields in Settings > Issues > Custom fields with the EXACT same name as the one in the Team-managed Project, they should get copied over. You don't have more than one custom field with that same name in the shared custom fields above do you?

Mavi_azjump

looks like there is the same name but different approach (one is a text field, and another one is a drop-down)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud