nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Done tickets are moved to next sprint even they have DONE status

tipi.chaibamrung@posti.com

I have 84 tickets show in "Done" column and all of them have "DONE" status. Column mapping has status = DONE and REJECTED. And this "Done" column is at most right.

However some of these tickets don't have Team label assigned or have multiple values.

When trying to complete the sprint, Done tickets are detected less than amount show in the board.

What could be root cause?

Accepted answers

All comments

Vishal Biyani_2pr07j

tipi.chaibamrung@posti.com

Are all the 84 tickets that are you are referring to a sprint in Done statusCategory? if not, that will explain why some of the open tickets are moved to next sprint or backlog

tipi.chaibamrung@posti.com

Yes they are. Some of them are not sub-task tickets and it still move to next sprint.

Sanam Malleswari

Hi tipi.chaibamrung@posti.com

Possible Root Causes:

Resolution Field Not Set: In Jira, issues are considered "done" only if the Resolution field is set. If this field is not set, even if the status is "DONE", Jira might not count them as completed
Sub-Tasks Not Completed: If there are sub-tasks linked to these tickets that are not marked as "Done", the parent tickets might not be considered complete
Filter or Query Issues: The board filter or query might not be correctly configured to include all "Done" tickets. This can cause discrepancies between what is shown on the board and what is counted when completing the sprint
Multiple Values in Team Label: If tickets have multiple values in the Team label, it might cause issues with how they are counted or displayed.

Steps to Resolve:

Check Resolution Field: Ensure that the Resolution field is set for all tickets in the "Done" column. You can do this by adding a post-function in the workflow to set the Resolution when moving tickets to "DONE".
Complete Sub-Tasks: Make sure all sub-tasks are marked as "Done". Jira requires all sub-tasks to be completed before the parent issue is considered done
Review Board Filter: Check the board filter or query to ensure it includes all relevant tickets. Adjust the filter if necessary to capture all "Done" tickets.
Simplify Team Labels: Ensure that each ticket has a single, clear Team label to avoid confusion.

Vishal Biyani_2pr07j

@Sanam Malleswari

Nice explanation!!!

In terms of 4th point, I see Team field (provided by JIRA) is a "single select" Field in my cloud instance.

Is there any setting that you know of using which multiple Teams can be assigned to an Issue?

Vishal Biyani_2pr07j

tipi.chaibamrung@posti.com

can you run below query

project = Your Project and Sprint = <sprint that you want to investigate> and (statusCategory != Done or resolution IS EMPTY)

See if this returns any issues

Sanam Malleswari

There is system field Team is there in Jira cloud software.

tipi.chaibamrung@posti.com

it returns more than 70 rows ... so I don't understand why clicking "Complete Sprint" button, it tells only 10 items

tipi.chaibamrung@posti.com

I think what I could try next is this suggestion:

Simplify Team Labels: Ensure that each ticket has a single, clear Team label to avoid confusion.

because current board pick tickets from 2 old boards so we have multiple team labels assigned.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-cloud