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; } } }

Bulk move issues from team-managed to company managed

Arthur Harutyunyan

Hey all,

I have a team managed project where I have >5k tickets. There are only Epics, Tasks and bugs, and lot of custom field configured in that team managed project.

I want to migrate from existing team managed project to a new Company managed project. I know, and I have read lot of articles regarding this topic but decided to raise this issue again

Problems:

1) I have Tasks in team managed project and I want to change Task -> Enhancement in the new Company managed project

2) I have lot of FixVersions configured in team managed project, and I want to keep them in new Company managed one

3) I have lot of Custom fields which MUST be kept in the new Company managed project

4) I have Sprints in team managed project, and I want to create new ones in Company managed project and associate the corresponding tickets with the new sprints.

Bulk Move wont do the job, because I will lost the Custom Fields data. And because of this I decided to go with the "Bulk Clone" direction

I know there are few plugins that do the magic, but with some limitation. For example, with "Deep Clone" I could not manage to change the issueType when cloning (See point 1)

The Export/Import is very dangerous, because it is too much complicated and tricky and most likely I will lost some important data when importing

So, guys, please help me to understand what is the best option to solve my Use Cases.

Thanks,

Arthur

Accepted answers

All comments

Ste Wright

Hi @Arthur Harutyunyan

Main page on doing this without Apps is here: https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/

Some things I'd consider doing if I wasn't using an App:

Move the data without modifying the Issue Type - then modify it in the Company-managed Project (CMP) once the move is done
For Versions, copy this data to another (global) custom field - eg. a text field - then recreate/reassign them once the move is complete. You could probably do both actions using Automation
Recreate the custom fields in the CMP before doing the move, then you can move this data over to them, assuming these fields are created in the TMP only, and not shared global fields
If it's only new Sprints - you can do this in CMP without any additional features, it's just native

^ I'd be testing this with some test data first however. Create another Team-managed Project (TMP) and put in some test data, then attempt the move and highlight anything which doesn't work as intended.

---

Some of the steps above (like the recreation of custom fields) are needed regardless

Otherwise as you mention, cloning is an option - you could either...

Use Automation. This would require some trial and error depending on your specific setup, but it is possible to clone an Epic with its children using Automation
Use an App to assist you, like Deep Clone, Elements Copy & Sync, or Clone Plus for Jira

---

For Automation, just be mindful of usage limits on Standard - see limits here

Ste

Arthur Harutyunyan

hi @Ste Wright thanks for this detailed answer.

I have already tried a lot of options and yes, I think the most applicable option is to:

1) Clone all the tickets from TMP to CMP using the "Deep Clone" app
2) Bulk change the issueTypes from Task -> Enhancement
3) Manually set the proper custom fields data (Customer, Platform, Test Case Path). Or automate this process using Jira Automation (should be possible)
4) Manually create the same sprints and re-assign tickets to the new sprints. I think I can use Automation also here.

Anyway, I will try also the other plugin "Elements Copy & Sync - clone Jira issues" to come up with the final decision.

Do you think the "Elements Copy & Sync - clone Jira issues" is better than the "Deep Clone" or they are almost the same ?

Thanks,

Arthur

Ste Wright

Hi @Arthur Harutyunyan

Each App has some unique features and differences.

I'd give each a go in a test Project, or all 3 offer free licensing for up to 10 users

Ste

Arthur Harutyunyan

ok thanks @Ste Wright I tried the other one as well, and it seems yes, the only option is "Deep Clone".

Anyway, let me ask one more question:

Would it be possible to set the corresponding custom fields value from the currentIssue to the clonedIssue using Jira Automation ?

It would look something like this:

if currentIssue.customField is NOT EMPTY then SET clonedIssue.customField.value = currentIssue.customField.value

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud