Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to consolidate two projects into one in JIRA?

 

1 answer

Hi Ishita,

You can use a bulk operation in order to move (and as such add) all issues from one project into the other one. Basically, go to the issue navigator, select all issues from your source project (Project = <your source project>), then select Bulk Change and move them to the other project.

There are a few things to consider before you start, though:

Both your source and target projects have configuration schemes behind them:

  • an issue type scheme
  • a workflow scheme
  • a screen scheme
  • a field configuration scheme
  • a notification scheme
  • Components
  • Versions
  • A permission scheme

Definitely compare the configurations of your projects and check whether everything you need in your target project is actually there. Add the components and versions you might be missing in the target project. Check if all custom fields you have in your source project are also available in the target project.

Should there be differences in terms of issue types and workflows, consider what you want to achieve. You can add the issue types and workflows of your source project to the target project, or you can decide to migrate issue types and statuses from your target project into other issue types and statuses in your source project. JIRA will present you with a wizard to make the mappings of your choice during the bulk move process. It is important that you have figured out the mapping rules you want to apply beforehand, so you don't get taken by surprise when you are in the middle of the actual move.

Finally, each project has its own project key, which is always the first part of the issue key, the unique identifier of each JIRA issue. Be prepared that the issues you are moving from the source project will get a new issue key in the target project, prefixed with the project key of this target project. JIRA will store the old issue key with the moved issue, so in searches you will still be able to find the issue based on the old key. But the new key - as said - will be different.

Hope this helps!

 

Thanks. it worked for me.

Like # people like this

Looks like the way to go. What about relationships between issues (child-parent; other links). Will these still be available on the new issue-keys?

Like Stuart C likes this

If the parent and child move together, Jira bulk move will maintain the links.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

New Cloud Apps Roundup - Spring 2021

Atlassian's marketplace partners have had a very productive start to 2021! Since our last roundup, our developer community has added over 160 new cloud apps to the Atlassian Marketplace to help you...

124 views 3 14
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you