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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

What are the considerations when consolidating multiple projects into a new project?



My team needs to consolidate multiple Jira Cloud classic projects into a new project (on the same instance).  We plan to do this using the bulk move function, and I understand that the references to the old issue keys (e.g. in issue links and comments) will redirect the user to the new issue keys. 

Other than mapping the issues types, custom fields, workflows, status, user permissions, are there any other configurations we need to consider?

Is it possible to delete the old projects after all the issues have been moved over to the the new project?  Will the reference to the old issue keys be retained after the old projects are deleted?

I'm wondering what is the impact to the old issue keys used in:

  • Bitbucket Cloud
  • JQLs (in filters and kanban/scrum boards)
  • Confluence Cloud pages (and macros)

Appreciate your advice and suggestions.


Thanks and regards,


2 answers

I shall attempt to answer my own question. :-)

My colleague and I did some tests in a cloud instance with Jira, Confluence and Bitbucket. We observed the following after moving issues to another project and deleted the old project:

Used a saved filter which queries issues from several different projects.

A) In Jira Cloud

  • Dashboards gadgets worked only with the saved filter but not for the old projects
  • Issues mentioned in comments display the new issue keys after issues are moved
  • Attachments in an issue remain unchanged
  • Issue search works for old issue key (new issue key is displayed in the search result)

Did not work

  • Saved filter with issue key(s) used in JQL did not work


B) In Confluence Cloud (with randomly picked macros)

  • New issue key is automatically displayed in the Confluence page where it is mentioned
  • Displaying a saved filter in Confuence (using copy & paste URL of filter) works fine
  • ‘Jira Issues Calendar’ Macro using a saved filter works fine

Did not work

  • ‘Jira Road Map’ Macro for the old project did not work
  • JIRA Issue/Filter used with specific issue key does not work


C) In Bitbucket Cloud

Only within Jira, the new issue keys are displayed when viewing

  • branch
  • commit
  • pull-request

Bitbucket continues to display the old issue keys with hyperlinks after the issues are moved.  These are then redirected to the correct new issue keys.  However when the old project is deleted, the old issue keys became plain text, the hyperlinks are lost.


Considerations when moving issues to another project, and when deleting a project

  • Re-locate (move) the scrum and kanban boards to another project as well BEFORE deletion.
  • Create the same (or similar) components and versions in the destination project.
  • Ensure that the issue types, screens (fields), workflows (statuses), priorities are available in the destination project, for mapping during the bulk move of the issues.
  • Ensure the right permission schemes, notification schemes, and/or issue security configurations are set up in the destination project.


  • Audit dashboards, saved filters, any automation or integration scripts which refer to projects or hard-coded issue keys.
  • Confluence pages with macros which refers to projects or hard-coded issue keys


Not sure if I've missed out anything else. Comments and suggestions are welcomed.

Like Vickey Palzor Lepcha likes this

That is some comprehensive testing result there.

Thank you Marianne - you seem to have answered more than what we were expecting. You rock.

Interesting question - I'd love to see someone reply this.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events