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; } } }

How to Handle "Done" tickets that are completed between sprint end and sprint start

Kiley Bublitz

The past few sprints, my team has ended up not completely finishing a few tasks. These tasks are usually in "PR Review" and "QA" when we close the sprint on Monday. We do not start the next sprint until Tuesday. Between the end of the last sprint, and the beginning of the sprint on Tuesday, some of those tasks are moved to "Done". The issue I am having with this is that they show up in our next sprint board as "Done" and increase our total sprint points for the next sprint. Is there anyway to prevent this behavior?

Accepted answers

Bill Sheboy

Hi @Kiley Bublitz -- Welcome to the Atlassian Community!

The sprint scope includes what was in the sprint when it started, and so...one way to address this symptom is remove the completed items from the sprint before starting it. The key is finding them using JQL and then removing the future sprint from their Sprint field.

I recommend pausing and discussing this symptom at a retrospective to better understand what is happening. It seems the team does work during a sprint to deliver value and then that vanishes from tracking / analysis / review / etc. before any review and retrospective. This may indicate challenges with planning, focus, etc.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Kiley Bublitz -- Welcome to the Atlassian Community!

Kind regards,
Bill

Kiley Bublitz

Hi Bill,

Thank you for your quick response. If I remove them from the sprint in their Sprint field will that result in me having "Done" tasks hanging out in the backlog?

Warmest regards,

Kiley

Bill Sheboy

No, and the speed of removal depends on your project type:

For a company-managed project, they will vanish from the backlog when marked as "Done"...which is why JQL (or viewing the issue directly) is needed to remove the sprint value.

For a team-managed project, I believe you will need to refresh the backlog page in the browser after removing them from the sprint to make them vanish.

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-cloud