Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

Bulk move issues from one "team-managed software" project to another "team-managed software project"

Edited

We currently have two team-managed software projects, ABC and XYS. We want to simplify and move every issue from ABC to XYZ, so that we will have only one active project. 

 

I found documentation on what happens when I move issues from a team managed to company managed and vice-versa, but no articles about moving issues between projects.

 

The outstanding questions I have are:

  • Will the old ABC-123 link redirect to the new XYZ-456 issue?
  • If users exist on both boards will the assignee remain?
  • Will issue status carry over?
  • Will issue relationships to other issues carry over?
  • What data, if any, might I lose?

 

2 answers

Hi @Gui Annunciacao 

 

I would recommend to navigate to Issue navigator, available on the left-hand side menu.

Screenshot 2021-12-01 at 18.39.24.png

If Issue navigator is not enabled:

  1. Navigate to Project settings -> Features 
  2. Turn on Issue navigator

 

Then filter issues (if needed) and perform bulk action on the issues you need to move.

 

To do so:

  1. Select more (•••) (on the top right corner of the Issue navigator) and choose Bulk Change all <n> issues.
  2. Select the issues you'd like to perform the bulk operation on, and select Next.
  3. It will open a "Bulk Operation" screen for you in the new tab.
  4. Once you get to the "Choose Operation" step, choose Move Issues and select Next.
  5. Then follow further instructions appearing on the screen.

Will the old APPS-123 link redirect to the new PLAT-456 issue?

Yes

If users exist on both boards will the assignee remain?

Yes

Will issue status carry over?

Yes

What data, if any, might I lose?

It shouldn't. Normally JIRA will inform you if some of the data is not available in the project you are transferring issues to, and will let you to action on such cases one by one. For instance, you need to make sure that same components exist on two projects otherwise you'd have to find a replacement for missing components or keep it empty.

0 votes
Jack Brickey Community Leader Dec 01, 2021

One of the key things to consider before proceeding is how similar or different the configurations are between the two projects. The reason why this is important with TMP is that each project is self contained. So custom fields that you've added in one project don't carry over to the other project.

With that said, I would try to move a single issue or two and then access how it went. If it went smoothly, and all of the other issues are similar, then simply do the bulk move. If not maybe you would want to consider exporting the issues to CSV and then importing them using that file. This will allow you to massage the CSV file to align with your new TMP project.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
Community showcase
Published in Jira Software

👋 Looking for 15-20 volunteers to test Atlassian training content

Hi everyone! Are you interested in beta testing Atlassian University’s newest (unreleased!) training course? We’re looking for 15-20 volunteers to test our newest training course, Basic reporting...

469 views 19 23
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