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

tipi_chaibamrung_posti_com
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 11, 2025

 

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?

 

2 answers

0 votes
sanam malleswari February 11, 2025

Hi @tipi_chaibamrung_posti_com

Possible Root Causes:

  1. 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

  2. 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

  3. 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

  4. 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:

  1. 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".

  2. 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

  3. 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.

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

Vishal Biyani
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 Leaders.
February 11, 2025

@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?

0 votes
Vishal Biyani
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 Leaders.
February 11, 2025

@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
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 11, 2025

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

Vishal Biyani
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 Leaders.
February 11, 2025

@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

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events