Merging 2 projects


I have two JIRA projects for the same client (one for marketing and the other for development). I want to know if it the best way is to bulk import the issues from one project to the other, and what are the consequences of doing this (eg. a change in the issue numbers, problems with attached files, etc).

Thank you!

1 answer

This widget could not be displayed.

Hi Melanie,There are multiple consequences and a few are:

  1. Project key will be different and you may need to update all your filters
  2. Workflows may not match and you may lose data integrity
  3. Field schema may be different and need better planning to avoid loss of data
  4. Default Assignee may be different between the projects and may cause issues
  5. Any reports generated out of the projects may need to be verified and updated (Ref: easyBI)

Question: Are you planning to move all the issues from one to other or only some of them in bulk? What is your goal?

Additional Info:

I have been through the path and I would suggest to use Bulk Clone to clone the issues rather moving the issues. You will have to analyze the workflows on both source and target projects to understand how many transitions you will have to go through and create a plan for doing the exercise.

  1. Bulk Clone works good at JIRA Server and may not be available for Cloud.
  2. There are limitations on number of issues you can clone in an attempt and that can be adjusted by system administrator if required.
  3. Closed issues on your source projects will appear as New after bulk cloning and you will have to do bulk updates too.

Hi Guhan,

Thank you for answering me! 
Both projects have the same workflow, scheme and default assignee, so that won't be a big problem.
We have one project that's only for the marketing issues of the client and the other one that is for everything else. The idea is to move all the issues (almost 400) from the marketing project to the other one and only have one project for each client. But I wasn't sure what the consequences were, so before doing it I wanted to do some research.

Thanks Melanie,

Suggestions: Collect statistics on number of issues by component, issue type, and status. Plan to disable webcast and outgoing e-mails, then do the bulk clone and required updates, then enable webcast and outgoing e-mails. I have done it for 36K+ issues without any exception. If you need further help, I can be contacted.

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted 9 hours ago in Statuspage

What are your best incident management tips and stories? #HugOps

 👋Community members! Downtime happens. And great incident response takes a village. Teams like Support, Dev, SRE, Ops, IT, and Marketing have to come together to resolve the problem while keep...

28 views 0 3
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you