automation rules

[Norlin Md Noordin]

i used the automation rule to set Resolution field to automatically be updated to unresolved whenever an issue is moved out of the Done status to any other status, the resolution field is updated accordingly to 'unresolved' based on the rule, however, the backlog is still showing the issue as strikethrough .. how do we resolve this?

[Lucas Modzelewski _Lumo_]

Actually, you don’t need automation for that - you can simply use a post function to clear the resolution field.

This article outlines best practices for handling the Resolution field in Jira Cloud (but the same principles apply to Data Center as well):

https://confluence.atlassian.com/cloudkb/best-practices-on-using-the-resolution-field-968660796.html

[Gor Greyan]

Hi Dear @Norlin Md Noordin ,

Setting the "Resolution" field to Unresolved, doesn't actually clear it. Jira considers any non-empty value in the Resolution field as meaning "resolved". Unresolved is typically a placeholder used when the field is empty, not a value that should be set manually.

Solution.

You should clear the "Resolution" field instead of Setting it to "Unresolved".

In the automaion's action, where you set the Resolution, user "Edit issue Fields" and clear the Resolution field(do not set it to a value).

Or you can user post-function, selecting "Clear Field" and choosing Resolution field.

If you have any questions, feel free to ask.

[Yi Meng]

@Norlin Md Noordin 

Normally, we do it through workflow post-function. You can add a post-function in your workflow for the issue type to clear the 'Resolution' field if you transition it out of the 'Done' status. By using this post-function, Jira will clear the resolution and resolved date for your issue. And the strikethrough will be cleared. 

For your automation rule, I don't know if you can clear the resolution or you actually set the resolution as 'Unresolved'. If there is a value in the resolution field, you will be able to see the strikethrough on it. I think that's the reason for your case. 

[Norlin Md Noordin]

Done status is in the last column.  So all tickets that are done would have a strikethrough.

We moved the issue to the Testing status which is in the middle (in-progress) column.  The resolution status correctly reflects as 'Unresolved' in the issue, however, the issue in the backlog is still showing as strikethrough. 

[Calvin]

• resolution status correctly reflects as 'Unresolved'

Apologies if I missed it, do you mean that the resolution is "Empty" which from what I understand is what it is when a ticket is not resolved. Or do you mean that a resolution is set, and that resolution is an "Unresolved" value.

[Calvin]

Is it in a status thats not in the one thats in the Kanban Column on the very right.