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
4,364,699
Community Members
 
Community Events
168
Community Groups

Migrate Sprint Reports and associated issues from one project to a new project

Hi there, I have completed 15 sprints in my current JIRA project and therefore have 15 sprints reports with the associated issues within each sprint outlined.  

 

I would like to migrate these sprint reports with the associated issues from my current JIRA project to a new JIRA Project. I cannot find anything online that says that this capability is offered. 

1 answer

1 accepted

1 vote
Answer accepted

Hello @Arjunan Ranjit 

Sprints are associated to agile boards, not to projects.

If you change the filter associated with the board, that will affect the history of all the sprints associated with that board.

So, in theory, if you use the Move Issue feature to move the issues to another project, and then update the board filter to reference that new project, your sprint history information should remain intact, remain associated to the same board, and reflect the issues as they have moved to the new project.

Does the destination project have the same issues Statuses and workflow as the source project?

Hi @Trudy Claspill , 

Thanks for getting back to me so quickly. First things, the destination project has the same issue status and workflow as the source project. So I did the following as you mentioned (using test features) except for 'update the board filter to reference the new project' - not sure what you mean by this. However the completed sprints were not visible on the destination project when within Sprint Reports. 

(1)  Within my completed sprint report and click on View in Issue Navigator. Picture1.png

(2) Bulk Change > Move Issues to target project 

Picture3.png

(3) Within Destination Project --> No Sprint Report 

Picture4.png

However issues have successfully been moved moved, as can be seen through the Done Filter within the Issues Section. 

Arj

Are you working with Team Managed (next gen) or Company Managed (classic) projects as the source and destination?

When working with Company Managed projects, the agile boards are based on Filters, specifying what issues are to be included in the board. And the Sprints are associated to boards. The board filters can be created to cover multiple projects, so boards and sprints don't belong to a specific project in that case.

If you are working the Team Managed projects, then the board and sprints are associated to a project, and my suggestion will not work.

Jira automatically deletes closed sprints and reports when issues are moved from project to another. It’s a reported bug from 2016

Thanks Trudy for the answer on this and Mohammad for the warning!

 

It seems the Jira bug is filed here: https://jira.atlassian.com/browse/JSWSERVER-13333 -  but the good news is that there are workarounds including temporarily re-opening the closed sprints, or using CSV import./ bulk edit to fix up the data after moving. I think data fixing is the approach I will try when I have to do this in a few weeks time. 

Just to confirm - Has anyone actually reopened the old sprints prior to a bulk move from team managed to company managed and had the velocity report history populate? Does this impact anything if a sprint is open during a bulk move?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events