Forums

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

JIRA disallows completing sprint due to incomplete sub-tasks, that are not even there in the Sprint

Debashish Chakrabarty
January 25, 2021

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.

image.png

Another Strange thing:

  • When I search for issues with query "Sprint in openSprints()", I see these only the subtasks related to the two culprit issues there, with the Sprint column clearly showing the next Sprint ID. The parent story doesn't appear here.
  • When I search for issues with query "Sprint in futureSprints()",  only the two parent stories show up there, not the subtasks beneath them. 

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.

1 answer

1 accepted

1 vote
Answer accepted
Dieter
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
November 20, 2011

Definitely whenever you want to track the status of an entity (be it real world like a device or something abstract like a requirement or a bug) JIRA is a good candidate to enter the play.

Besides what you mentionned I like to get automated reminders from subscriptions, e.g. for overdue issues or weekly reports ai have to do. Excel can't do that for you, it's passive until you open it. Using customized mail templates you can automatically provide reports for managers as soon as critical actions have been taken, e.g. when an expensive equipment breaks.

The problems you will probably face with JIRA is to get acceptance for the user interface by end users (not developers). But since there is SpeakEasy you can also better customize the UI for more unexperienced users and hide away a lot of all the bells and whistles in JIRA.

Rob Davis
November 20, 2011

+1 and accepted. What I wanted to read :) But what you say makes sense to me. Thank you. I'd welcome anyone else to contribute too.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events