Forums

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

Jira Will Not Close the sprint

Tom February 22, 2018

I am attempting to close a sprint. When I look at it:

a) All story points are in the "Done" category

b) All statuses are set to "Closed"

I still get the message that 5 issues are incomplete. I have tried searching (there are sub-tasks in the stories) but I cannot find a story or sub-task that is not "Closed."

Can you please give me a tip as to what I might check? I see a number of threads on the same topic, but I have not been able to solve the problem using the answers provided in them. Thanks.

2 answers

1 vote
Jack Brickey
Community Champion
February 22, 2018

@Tom, a couple things to use to investigate...

  1. Go to Board Settings and look at Columns. Do you have any unmapped statuses? If so the incomplete items could be hiding there. If unmapped status exist, you can temporarily expose on the board - create a new column and drag the unmapped statuses there. Go back to board and have a look.
  2. use the following jql or similar - project = xxxx and sprint = yyyyy and status != DONE or whatever your done status is.
Tom February 22, 2018

Hi Jack,

I double-checked, but there are no unmapped statuses in the board. I also ran the query above, where status != Closed and I get zero issues.

I know we converted from one JIRA project to a new one as this sprint was being prepared (prior to activating the sprint, though) so I've been looking for other signs of difference - I cannot seem to find any, though.

Jack Brickey
Community Champion
February 22, 2018

aha....i think that might be the smoking gun...let's explore. What exactly do you mean about converting from one project to a new one? if you run this simple filter what do you see...

sprint = xxxx

anything there look out of place? any issues associated to a project that is not currently associated to your current sprint board? can you share your board filter?

Tom February 22, 2018

My project is among hundreds of projects, so if I do an issue search on sprint = "Sprint 4" alone, I will absolutely get back many projects' sprint 4. Is there a project-specific name I can use in the JQL?

My JQL has been: project = <project> AND Sprint = "Sprint 4" AND status != Closed

I've also tried without the status check.

Tom February 22, 2018

This is a shot in the dark, but if a GIT merge failed or something code-related, would JIRA deem the issue to be incomplete? How could I search for that?

Jack Brickey
Community Champion
February 22, 2018

 

well i was going down the path that possibly an issue from a project other than the one defined currently by your board was added into 'your sprint 4' at some point and then your boards filter changed resulting in removing that issue from the board but not the sprint. Is that possible? If so do you know what the other project(s) might be?

do you have a lot of "sprint 4" that are not closed?

you could try sprint = sprint 4 and sprint in openSprints()

Jack Brickey
Community Champion
February 22, 2018

no. Jira works off of the right-most column for issues done when closing sprint. so if all issues are in the right-most column then it should close.

Tom February 26, 2018

Thank you, Jack, for all your input. I wish I could provide a hint of anything else I see out of the ordinary. I just don't see anything out of the ordinary. Is there a way I can query what JIRA is seeing? I don't know how it defines "Incomplete" other than the JQL you mentioned above.

Jack Brickey
Community Champion
February 26, 2018

@Tom, i have pinged other Community Champions to have a look at the thread to see if they have other ideas. I expect you will see them chime in today.

Like Peng XI likes this
0 votes
Tom February 27, 2018

I found the problem. We have two JIRA projects linked together: one for Delivery and one for Test. There were five bugs, test cases, and other test artifacts that belong to the test JIRA, but are somehow linked to the Delivery project, that cause the sprint to remain open.

I'm following up with our JIRA administrators to see how to address the issue, as it seems to be an internal flaw, created by how the JIRA projects were linked together.

Jack Brickey
Community Champion
February 27, 2018

ah, ok then. Good sleuth work Tom!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events