Forums

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

Moving issue to the next sprint

Miha Pecnik
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!
January 14, 2019

Hello,

I have a problem with moving issue from active sprint to the next one. 

2019-01-14 18_19_59-Slack - Sixt.png

The problem is that Customer App Bugs is not my next sprint. It is not even sprint of that project. I checked the IDs of sprint and it is not even sequential, if that would have any impact. On other projects everything works fine.

How can I fix that?

Thank you

1 answer

0 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 16, 2019

What version of Jira Software are you using?

The screenshot you posted looks to be of the Move issue function.   But you describe moving issues to another sprint.  This is not the same as using the close sprint action.  When you use that in the latest versions, it can prompt you specifically which sprint to move the issue to or move it to the backlog.

closesprint.png

 

In your case, using the move function can change the entire project of the issue in question.   I would be interested to see if you can either use the close sprint function, or change the sprint value before moving the issue if you want to use that specific action here.

Suggest an answer

Log in or Sign up to answer