Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to migrate completed and active sprint from one project to another project

Dnyaneshwar Ramesh Borase
Contributor
November 15, 2018

Hello team,

We have started working on release from last month and we have completed three sprints and 4th sprint is started under this release in project A.

Now we got information from project manager that all these sprints and efforts has to be added in new project B.

 

Do we have any way to migrate all these completed sprints, ongoing sprint, version and efforts logged to B project?

 

Thanks!

2 answers

0 votes
Anton Miloushev
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 2, 2023

I just did it following the below steps:

1. Put all items you need to transfer to a new project in a separate sprint, 

2. Select all tasks 

3. Right click on any task and select Bulk Change

Bulk change.png

4. Follow the steps, you should have the sprint in the new project (if there are any tasks which couldn't be transferred, you will have the same sprint in the old project as well. Relationships between the tasks will be lost.

0 votes
Ollie Guan
Community Champion
November 15, 2018

Hi @Dnyaneshwar Ramesh Borase,

As far as I know, Sprint is not strongly associated with Project. The information displayed in Scrum Board depends on the configuration of the Board filter. You can try the following two ways to handle this case.
1. Modify Project A's Board filter to include all Issues of Project A and Project B.
2. Move Issue from Project A to Project B and create Project B's exclusive Scrum Board.

Hope this help.

Dnyaneshwar Ramesh Borase
Contributor
November 15, 2018

Thank for the reply.

Can we migrate all version and efforts logged from project A to B project?

Ollie Guan
Community Champion
November 16, 2018

Hi @Dnyaneshwar Ramesh Borase,

The effort information is stored in the Issue and can be moved to Project B synchronously.


However, the version cannot be moved directly to the new project. It is recommended that you manually generate the version in Project B. When you move the Issue, the system will prompt you to select the version that matches the project B.

mpietro40 January 18, 2023

HI, I've a similar problem, the issue is that when I moved the issue from project A to project B I loose the connection with the original sprint.

Why is this happening?

I can't reassign the issue to the closed sprint

Suggest an answer

Log in or Sign up to answer