Hi,
I just completed a sprint and had a few Closed Task items. These items for some reason moved to my next sprint.
1. I dont have sub-tasks under these
2. Closed is the last status in the right column
3. Resolution has a "check" mark Done or Wont'Do.
4. In another sprint on the same project, thier done items did get cleared. It is the same workflow.
Any ideas?
@Meytal BM I am having the same issue - how did you end up resolving yours? ~Krisi
Everything 'done' has the resolution set?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No idea why. Not having the resolution set is usually the reason.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yeah, that's strange. Do you see a 'Sprint' field being populated and updated with the new sprint name?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Carlos Garcia Navarro Yes, its crazy!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you please create a new scrum board (replicate the existing one) to see if the same behavior is observed?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hmmm, this is quite odd based on what you have shown and said here. Just to confirm, you are saying that you completed the sprint and issues in the right most column ended up going back into your backlog or future spread correct? Something is missing or being overlooked here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Meytal BM , can you reengage here?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Jack Brickey Yes.
1. I close sprint
2. I decide to move the items to next sprint candidate
3. I start new sprint candidate
4. I see those previous sprint Done items in New sprint
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So when you close the sprint do you get a notification that issues are incomplete and will be moved to backlog or next sprint?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Jack Brickey Yes i did.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok in that image you are showing 46 incomplete. If you are saying that these 46 issue were indeed in the right most column of your sprint when completing the sprint the something is certainly wrong and you should contact Atlassian Support directly. I am still quite curious as to he differences between the issues seen as complete (2) and those seen as incomplete (46).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Jack Brickey the 46 are actually incomplete and NOT on the right column Done. The 2 are. I can't know if now it will be ok until end of this sprint which is end of nex Thursday. So i guess we'll have to wait and see whether anything under Closed column actually did NOT get moved over to future sprints. wdyt?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Understand. Definitely reach out to support if this reoccurs. Question - what are you doing with the previous complete issues that land back in the backlog? If you carry them over to the next sprint can I assume they simply show in the right most column from the start of the sprint?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Meytal BM - I have a similar issue in an inherited jira project. Did you manage to resolve it? If yes - can you share how and what was the root cause? Thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.