How to manage reporting when moving a project to another project?

[Krista Nicol]

I'm a Jira administrator at my company and we have some projects moving to different areas and out of their current projects - for reference, within our Jira projects, teams are separated by components so when we undergo team movement, they can utilize the component to bulk move their issues to their new project.

The issue we're running into is that the velocity report on the new project does not populate with the historical issue data from the original project. The resolution I found for this was to include the original project on the board query - this successfully populated the velocity report, but the sprint reports are no longer populating and it seems like the historical sprint data is lost.

Is there a way to move issues from one project to another without losing either the velocity report or the sprint reports?

[Teresa_DevSamurai]

Hi 

It is possible to move issues from one project to another in Jira without losing either the velocity report or the sprint reports by using the Jira built-in "Bulk Move" function, Jira plugins like "Jira Software Transitions" or "Jira Project Import/Export" or the "Jira Cloud Migration Assistant" which is a tool provided by Atlassian.

It's important to make a backup of your Jira data and test the process in a test environment before applying it to production. It's also worth consulting with a Jira administrator or developer to find the best solution for your organization based on the specific requirements and configurations of your Jira instance.

I hope this information is helpful to you