Finding issues that have all subtasks complete

[Andrew Stanton]

When completing a sprint I got the message 

X issues were incomplete (Y of which had all of their sub-tasks complete)

(X and Y are numbers)

How do I find issues like this?  With Azure DevOps I can use a link type query or treeview, but there does not seem to be an easy way to identify these within JIRA

[Trudy Claspill]

Hello @Andrew Stanton 

Unfortunately there is not a JQL filter available within the native Jira Cloud functionality to enable you to get that information simply. 

You could investigate third party apps that extend JQL search features.

You would also construct a filter to return all the sub-tasks for the issues in your sprint and then review the results. Natively Jira doesn't support filters based on filters, so you would have to provide an explicit list of the issue keys, like...

parent in (issueKey1, issueKey2, issueKey3)

[Andrew Stanton]

Oh Well. I guess my afternoon will be spent writing a script to use the REST API to figure this out. 

Thanks to Atlassian for telling me "there is a problem" and going to the trouble of counting the issues with that problem, and then failing to share that list... Not.

[Trudy Claspill]

You should be able to see the incomplete vs. complete issues in your board.

If the issue itself is incomplete, it will be in a column other than the one farthest to the right.

If an issue has incomplete sub-tasks, then those sub-tasks will show in those columns, with either a header line or the full parent issue card directly above them (depending on the swimlanes for your board, and whether you are working on a board for a Team Managed or Company Managed project).

Is that visualization not apparent in your board?

[Andrew Stanton]

Its company managed, and all the card columns have 0 count and no cards except for the Done column,

Rather than mess around with this, I'm going to tell JIRA to put these items into a new sprint to see if that will at least identify them. 

[Andrew Stanton]

And it identified some of them, mostly things that were resolved or rejected as being incomplete. Something is not right with our status transitions or something. Thanks for the help.

[Trudy Claspill]

For the issues in statuses mapped to the right-most column, are you ensuring that the Resolution field is getting set when they transition to those statuses? That is typically handled with a screen that shows during the transition and allows you to select a Resolution value, or is automated as a Post Function for those transitions.