"labelled as done" is irrelevant to the strike-out function.
An issue's display will take on the strike-out (in many places) when the resolution is set to a value. When the resolution says "unresolved", it is a display for us telling us "the field is empty", and it won't get struck out.
An issue's status, what column it is in on a board, whatever your "labelled as done" means, and so-on do not matter. The strike out happens when the resolution is filled.
You need to move the issues through a transition that sets the resolution (either with a post-function, or by having a screen with the resolution on it)
A typical way to do that is to temporarily add a transition back to the current status to your workflow. You could also edit it into the issues, if you are *very* careful to only try this when you know your users won't be active.
Thank you everyone for your help!
I contacted attlassian and below solved the issue:
"In your situation, I would recommend performing a Bulk Edit of the Resolution field for all of your tickets in the “Done” Status. You can perform that bulk edit to set the Resolution field from “Unresolved” to “Done”."
That's what I was getting at with
"You could also edit it into the issues, if you are *very* careful to only try this when you know your users won't be active."
The problem with that approach is that you have to put the resolution on the "edit" screen. But you must never put the resolution on the edit screen because it will cause all edits to resolve your issues. So you have to put it on-screen temporarily, while none of your users are active.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs