You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I am facing a strange issue. When I try mark a Sprint complete (that has some incomplete tasks, which should spill over to next Sprint), I get a message that the Sprint cannot be marked complete because two Stories (the story key is also displayed) have incomplete sub-tasks. The strange thing is that both these stories do not even belong to this Sprint and have been marked with the upcoming sprint.
Another Strange thing:
The two parent Stories and the sub-tasks with in them are in "TO DO" state, and the Sprint field for them show the Next Sprint, the sub-tasks inherit the field value from their parent. We use the "next-gen" JIRA and use the standard workflow.
That seems odd for sure as incomplete issues should move to next sprint of backlog. However, check to verify that the parents (stories) of the incomplete subt-tasks are not marked done/resolved. The story should remain open if the children are still incomplete.
Thanks for the reply. The two Stories JIRA objects to, do contain sub-tasks, but all these sub-tasks (as well as the parent stories themselves are in "TO DO" state), and the Sprint field for all of them show the upcoming Sprint (I even verified that using the Export XML option). They are also not linked to the current Sprint Agile board (and not now show-up on the board).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you clear the sprint field for the stories and sub tasks then check that the issues are in the backlog and retry?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Tried that, now the parent stories have moved to the backlog but the sub-tasks are still showing up in the "openSprints()" query. And still getting the same error message on trying to mark sprint complete.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
And you are sure the sub tasks sprint field is in fact clear? If you remove the sub tasks from the current sprint they should not show in the active sprint board and should not be blocking. Otherwise, I have to wonder if you have any addons that may be causing the conflict. Beyond the I would refer you to Atlassian Support. Or maybe others will chime in with ideas here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes Jack that's verified. I anyway always put the Sprint in the parent story only (that then cascades to the child issues). Once I removed it from the Stories it vanished from their sub-tasks as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If neither the stories nor sub-tasks are appearing on the scrum board and you still can’t complete the I recommend having Atlassian Support log in and have a look.
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.