Issue Summary

If you have a team-managed project and change the key of that project to a different key. Using the cloud-to-cloud migration tool will break the feature to only display sprints related to the source project. It will occur if you have a project in the destination cloud site where one of the previous keys matches the original key of the source cloud site Team-managed project.

It is a very specific behavior. As results using the mentioned feature will not display any sprints:

Steps to Reproduce

1. Create a team-managed software project in the source site with the WF project key, create a sprint, and create an issue inside it.
2. Update the project key from AB to ABC (for example).
3. Create a project in the destination site with the key ABCD
4. Change the project key from ABCD to AB, save it, and then change it to anything else (for example ABCDE).
5. After that, run the clout-to-cloud migration moving the project ABC to the destination site.
6. Once the migration is complete, if you try to associate the issue and check the box to only display sprints inside that project, it will not return any sprints.
7. If you run the rest API GET using the endpoint https://yoursite.atlassian.net/rest/greenhopper/1.0/sprint/picker?query=&maxResults=10&maxActiveSprints=5&projectKey=ABC you will be able to see that none sprint is returned.
8. If you run the same endpoint again removing "&projectKey=ABC", you can see that the sprint is associated with the wrong project key (ABCDE), and for that reason when the endpoint mentioned is triggered trying to find the sprints related to the project key ABC, no results are returned.

Expected Results

• It should return the sprints created for the migrated project.

Actual Results

• None of the existing sprints are displayed.

Workaround

1. Go to View all filters
2. Search for the name of your board, there should be a filter associated with your board.

   

3. Once you find it, click on the name of the filter, and edit the filter to change the project key to the correct key of your project, for example, ABC. After you change it you can save the new filter.
   
4. The issue is resolved and you will be able to display the associated sprints.