Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

None completed US not reported onto the next Sprint

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. 

1 answer

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,


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?

Edit - sorry, ignore me, answering the wrong question

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:

Best regards,


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

New Cloud Apps Roundup - Spring 2021

Atlassian's marketplace partners have had a very productive start to 2021! Since our last roundup, our developer community has added over 160 new cloud apps to the Atlassian Marketplace to help you...

82 views 1 12
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you