Done tickets being moved to the next sprint

[Marino Poletine]

When I release a version, the tickets that are done or declined are being moving to the next sprint.
How can I fix that?

[Marino Poletine · Accepted solution]

Fixed.
The resolution was to update that rule and then move the tickets out of done to any status and then move it back to done.
The rule is only applied to the newly updated tickets. It is not applied to old tickets.

[Mikael Sandberg]

Hi @Marino Poletine,

Welcome to Atlassian Community!

Those work items are moved to the next sprint because the resolution field is not set when they are moved to a done status category. You can read more about the best practice for resolution in this KB. In order to fix it I would use an automation instead of a transition in the workflow that the KB is mentioning. The automation can be a scheduled one an you can use this JQL in it:

statusCategory = Done and Resolution IS EMPTY

[Marino Poletine]

As you can see on the last picture, even if I set the resolution, the done tickets stays there

[Marino Poletine]

Also, that KB must be outdated. The steps do not apply to me as this option "Click post functions" is not available

[Mikael Sandberg]

@Marino Poletine It looks like you have a resolution called Unresolved, which goes against the recommendations for the field. You should never have a resolution called unresolved.

Yes, if you are using the new editor you do not see Post functions, in the new editor it is called Rules and the one you want to use is called Update an issue field.

[Marino Poletine]

That has been already done when the board was set

[Mikael Sandberg]

@Marino Poletine the way you have it configured you are clearing out the resolution instead of setting it to a value when moving to Done, and that would explain why Don work items are moved to the next release because resolution is empty.