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

Why are my closed tickets moved from a sprint to another?

Grégoire MANIEZ_b6byyv

Hello everyone!

I got a quick question: why are my closed tickets moved from a sprint to another?

2023-08-01 15 07 26.jpg

For instance, this epic and all its tickets were completed half a year ago (Fermée = Closed), but for some reason it's like they're still opened, as they keep being moved from sprints to sprints.

Is there a reason I don't get? My sprint statistics always get messed up as there are hundreds of tickets in this case.

Accepted answers

Cassie the Jira Mechanic

@Grégoire MANIEZ I bet although the status is "Closed" your resolution field is empty. A quick way at a glance to check if this is the case is by seeing if there is a check mark next to the status of the tickets in Closed. Jira considers the lifecycle of a ticket to be finished truly only when the resolution field has a value. You can set this using a transition screen on the closed status or a post function in the transition in the workflow.

Here is some documentation about the resolution field.:
Best practices on using the "Resolution" field | Atlassian Cloud | Atlassian Documentation

All comments

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

The usual reason for this is that the issues are not in the last column of the board. Or they still have open sub-tasks (also not in the last column of the board)

Cassie the Jira Mechanic

Grégoire MANIEZ_b6byyv

This is the workflow we're using :

2023-08-01 15 57 31.jpg

S since Closed is in green, in theory Jira recognizes these tickets as completed. My closed tickets don't display on my board.

For some reason, for many tickets there is no problem, it appears to be old tickets only. Perhaps I have done something at some point that makes it work the way it should, like tickets in Deployed moved to Closed automaticaly when the sprint ends.

Is there a way I could perform an action (even manually) on tickets with the issue to set them as completed?

Grégoire MANIEZ_b6byyv

Thanks Cassie, I'll have a look at it!

Grégoire MANIEZ_b6byyv

I managed to do everything on this best practices document and now I have this "Done" mark on all my completed tickets.
I will see when my sprint ends if the sprint moves along or not.

Thanks!

Nic Brough -Adaptavist-

The resolution is irrelevant to the board, and the board is where your sprint is based. As I said before, your issues need to look "done" if you don't want them to move to the next sprint, and that means that they (and their sub-tasks, if any) are all in the last column on the board.

Cassie the Jira Mechanic

Now that you have fixed it for future tickets this is how to fix old broken issues:

create a scheduled automation using JQL to sift out only the issues you want to repair. I usually use the one shown here:

**NOTE: ( the day and time isnt important as we will force it to run when we are ready)

Then after clicking 'Save' you can 'add an action' and that action will be 'Edit Issue Field'. Once that is loaded you will click the cog 'Choose fields to set' then you will select resolution. Once you see it as below you can start typing in the resolution box the resolution you want it to be. If you are unsure use the drop down arrow to see your options.
(If you don't see this box make sure you click the dots/meatball menu and select 'SET'.)
fixresultions 2.JPG

Once that is done you can click 'Save' then you should be asked to 'Publish' the automation.
After its saved and publish you can now see the 'Run Rule'. Run the rule and wait. Once its finished check your tickets to verify fix. If all is well DO NOT FORGET TO disable the automation!

Let me know how it went!

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud