Sprints relation to issues moved from a project to other

[Dario Pereyra]

We wanted to discuss an issue we've encountered after moving part of a project backlog to another team-managed project. The problem is that the moved issues were previously included in the origin project's sprints. As a result, even after moving them, their original sprint relations remain intact. This has caused a bit of confusion, as the standard reports, especially the Velocity reports, from the target project now show data from both the target sprints and the original sprints. Consequently, the reports are quite a mesh and not very useful. I wanted to bring this to your attention and see how we can address this.

Is there any way to solve this?

Looking forward to your thoughts and suggestions on this matter. Thanks for your attention and cooperation.

[Clark Everson]

Hi @Dario Pereyra 

In regards of moving issues with sprints in them this is expected behavior. Sprints are actually not part of projects, they are part of boards. So the sprint IDs are tied to boards not to projects. 

What would need to be done when moving issues between projects is to first bulk edit them to remove the sprints and then after that you would move the issues. 

So 2 bulk actions

Best,

Clark