Is there a way to show if a subtask was completed in a previous sprint?

hvdploeg

Basically, we don't always complete all subtasks of a story within a sprint. So we add the story to the next sprint, but now we can't (easily) see which subtasks were done in the current sprint and which ones where already completed when we started the sprint.

Is there a way to show if a subtask was completed in a previous sprint? (like with a setting or a plugin perhaps?)

Ste Wright

Hi @hvdploeg

There isn't in standard Jira.

I see this as common practice though - a sprint tracks the completion of stories. A story can be broken into multiple sub-tasks - but even if you complete half those sub-tasks in a sprint, the whole story isn't complete. This means the whole story (including all its sub-tasks) move into the next sprint.

This is why sub-tasks can't be added to a sprint by themselves, nor show up in the sprint report. 

----------------

I couldn't locate an app for this - but I did manage to do something using JQL. So for example:

Sprint in closedSprints() and (Sprint in futureSprints() or Sprint in closedSprints()) and issuetype = Sub-task

^ This JQL provides you a list of sub-tasks where their parent story is in both a closed sprint and a future or active sprint. This provides you a view of the current status of those sub-tasks.

You could limit this to two specific sprints by getting their sprint IDs - such as:

Sprint = 10 and Sprint = 11 and issuetype = Sub-task

^ You can get their Sprint IDs from the sprint report - change the drop-down between sprints and the URL will change - take the ID from the end of the URL - &sprint=11

This doesn't give you a historic view but an active view of sub-task statuses when one sprint closes and another starts.

----------------

If you wanted a historic view I think you'd need to use history searches - for example:

resolution was EMPTY during (2020-01-01, 2020-01-31) and resolution is not EMPTY

^ This provides me a list of issues which were incomplete between those two dates, but are now complete. You could change those dates to be a sprint to see issues which were not resolved prior to the sprint's closure.

See more information on history searching on this blog.

Ste