This question is in reference to Atlassian Documentation: Moving an issue
Shouldn't be allow to change sprint when moving issues across projects?
I am right now in the process to reconfigure/reorder a project into different projects, and indeed old_project didn't have really good sprint definitions.
As I move the issues from one old_project to any of the new_ones, why not select the new sprint also ?
Many people fall in to the same trap that you have in thinking that a project and an Agile board are implicitly the same. Whereas in reality an Agile board is a representation of a group of issues that can be any of the following
The Agile board is based on a JQL filter and so whatever you can define as a JQL filter on your instance can be used as the basis for your Agile board.
So going back to your question I assume you have two boards set up using option 1 (single project all issues) and so when you move the issue between projects you want to also update the Sprint to match the appropriate board. As you can see options 3-4 (Which are all really variants of a board based on a more complex JQL filter) it would be possible for the issue to remain in the same sprint but be present in different projects.
As you are moving between projects and NOT boards it is necessary to allocate it to the correct sprint after moving.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
A picture tells a thousand words. And agility boards have just released their latest feature: cover images on issues – so now your board can tell a story at first glance. Upload attachmen...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs