Automation to resolve issues does not mark as resolved

Question

I have a very simple automation setup to transition an issue to resolved after 5 days of no response from customer. I choose resolved as the state to transition to and then choose done as the resolution field. This should resolve the issue, and it does set the status to resolved, but Jira still treats the issue as unresolved. Is there an additional step I am missing here?

John Funk · Answer

The Resolved field gets set automatically by the system.

rfisher · Answer

My automation is changing the status to resolved and setting the resolution to done but I haven't set the Resolved field. I will try that and see if it helps.

Thanks!

John Funk · Answer

Hi @rfisher  - Welcome to the Atlassian Community!

There are three things involved here - the status and the resolution field and the resolved field.

The status is usually something like Closed or Resolved or Done, and it is the last step in your workflow. It usually has a status category of Done (as opposed to In Progress or To Do).

The Resolved field is simply a date field that stores the date when the issue to move to a Done status category.

Finally, the Resolution field captures information as to the type of Resolution. It can be something like Done or Obsolete or Won't Do, etc. There are many options out of the box for this. When this field is populated, that causes the issue to have the strike through.

Can you share a screen shot that shows the status field and resolution field for the issue?