Issues not always marked as resolved when moving to Done column

[Will Henry]

I notice that when I move a story from a backlog column, directly to done, it is not marked as resolved. (There may be other cases where this happens, it has happened with several issues).

I have a special 'Resolution fix' transition that moves an issue from Done -> Done and use the Resolve Issue Screen. I use this transition to force to mark issues, in the Done column, as resolved, but why is this happening in the first place? Is there an underlying problem that needs to be fixed?

[Trudy Claspill · Accepted solution]

Hello @Will Henry 

Welcome to the Atlassian community.

Are you working with a Team Managed project or a Company Managed project? That information will show at the bottom of the panel on the left when you are viewing the project. I think you are working with a Company Managed project.

For a Company Managed you can set the Resolution field in two ways through Workflow Transitions:

1. Use a Transition Screen that includes the Resolution field, which it sounds like you are doing with your Done -> Done transition, allowing the user to pick the Resolution value.
2. Add a Post Function to each transition that goes to the Done status, and in the Post Function set the Resolution field.

You have to use either a Transition screen or the Post Function on every transition to leads to the Done status if you want the Resolution set when transitioning to that status.

In addition, if your issues can move from Done back to a non-Done status, each of those transitions should include a post function to Clear the Resolution field.

[Will Henry]

Thank you! This fixed it. I have two workflows (one for bugs and one for other issue types).   I have been using the generic 'All' transition for each status. I didn't realize that, in one of the workflows, the 'All' transition to Done had a post function that set the resolution field to Done. In the other workflow, the 'All' transition to Done did not have this post function. I am not sure why, but now it is fixed.