Issues marked as Done incorrectly after changing Sprint Board (Definition of Done)

[Leonard Whitehead]

One of our Squads had their Definition of Done set up to include both Release and Post Release Sign offs. After changing their Board to reflect our organisation level Definition of Done (i.e. ready for release but not deployed) a whole bunch of items in their backlog are marked as 'Done' incorrectly.

I've checked the Transitions and mappings but can't seem to resolve. Anyone dealt with similar please?

Please don't reply with the rule that Done has to be the last column on the Board as I've got 2 other boards with column to the right and they work fine :)

Attachment 1: How their Board used to Look

Attachment 2: What I Changed it To 

Here's the Problem in the Backlog

Thanks in Advance,

Lenny

[Alexey Matveev]

Hello,

What do you mean by marked as Done? Do you mean that the issue key is crossed out? If so, it means that you set the Resolution field on transition to this status. If you do not want to have the issue key crossed out, you should not set the Resolution field, when you move an issue to the Done status. 

If you do not have a screen with the Resolution field on the Done transition, then check if you have any post function in the Done transition, which set the Resolution field automatically.

[Shay McAulay]

I think what you are referring to is the 'crossed' out items in the backlog.

This represents in Jira that a 'Resolution' has been set, which an associated resolution dates.

You can manually go in and try to clear that field but I have had mixed success due to it being a controlled field in Jira.

This is another reason to no 'reopen' closed/done items but to create a new one and link it to the old one.

Best advice is to ignore it and it will eventually clear itself up as the work progresses through the new workflow and the correct resolutions and resolution dates get set.

Hope this helps.