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

Merging 2 projects into as single one

Samir Freelance

How can I merge 2 projects into 1 I need to copy attachements also

Accepted answers

MatthewC

If you use the Bulk Move you will need to make sure the configuration between the two projects is the same. You'll need to make sure that:

Versions are aligned between source & target projects
Any components that are in the source project are in the target project
Any custom fields are in scope for both projects
If you're using custom issue types, make sure that there is a corresponding (or sensible) default in the target project. if you jump to a new workflow, you'll loose some of the history which may have an impact on your workflow conditions (e.g. If the workflow you end up on has a condition that you've gone from State D -> State F before you get to State G then you can get stuck).
Run an itegrity check afterwards just to make sure all is OK.

Oh... and make sure it's done out of hours & you have a backup. The Bulk Move is good but it's very easy to wipe out data if you're not careful.

All comments

Markus Lepper1

Hi Samir,

you could use the "Move" function to move all issues from one project to another (=target) project.

BR, Markus

Samir Freelance

Thanks Markus can you please paste me some URL concerning the Move function or demo link..

where can i find the move ?

Betsy Walker

It's done with the Bulk Move operation. Note that bulk operations can be resource intensive, so if you're moving lots and lots of issues, you should perhaps do it off-hours.

Markus Lepper1

Right!

...BetsyW was faster

MatthewC

If you use the Bulk Move you will need to make sure the configuration between the two projects is the same. You'll need to make sure that:

Versions are aligned between source & target projects
Any components that are in the source project are in the target project
Any custom fields are in scope for both projects
If you're using custom issue types, make sure that there is a corresponding (or sensible) default in the target project. if you jump to a new workflow, you'll loose some of the history which may have an impact on your workflow conditions (e.g. If the workflow you end up on has a condition that you've gone from State D -> State F before you get to State G then you can get stuck).
Run an itegrity check afterwards just to make sure all is OK.

Oh... and make sure it's done out of hours & you have a backup. The Bulk Move is good but it's very easy to wipe out data if you're not careful.