None completed US not reported onto the next Sprint

[Sundaresen Rungasamy]

This is an something experienced by my team mate. he closed his Sprint and indicated to report the none completed US to be sent in the next sprint. Jira did not execute that , but instead sent the US to the backlog!. What could be the issue? 

As I always tries to find solution for everything, I am here being challenged as I couldn't figure out the problem. Thanks for your help. 

[Bill Sheboy]

Hi @Sundaresen Rungasamy 

If I am understanding you correctly, that is the expected, designed behavior.

When a sprint completes and there are remaining issues, you may choose to send them to a future sprint or to the backlog.  There is no option to "ignore" or "remove" issues which did not complete.  That decision is a choice for the team to make regarding the disposition of those items.

As work-around you could:

• Move the remaining items to done, and some how mark them as "abandoned".  To make this work update your board filter to ignore your "abandoned" issues designation, such as with a custom field, label, etc.
• Once the issues move to the backlog, decide what to do with them.

Best regards,

Bill

[Sundaresen Rungasamy]

My colleagues chose to send the remaining issues to the next sprint but Jira shifted them to the backlog which is not what was expected! 

Where is JIRA going wrong?

[Nic Brough -Adaptavist-]

Edit - sorry, ignore me, answering the wrong question

[Bill Sheboy]

Hi @Sundaresen Rungasamy 

I suggest locating some example issues you believe fit into this scenario you have described, and then review their History in the issue view.  That will show what changed and who changed it. 

If you still believe there is a problem where the issues did not move to the next sprint as expected, please ask your site admin to submit a ticket to Atlassian support to see how they may help: https://support.atlassian.com/contact/#/

Best regards,

Bill

[Sundaresen Rungasamy]

Thanks Bill