nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation - Unknown fields set during transition

phil.americus

I have automation set up so that when an issue transitions into status X it will automatically close it if a certain field is set. When I look at the audit log, sometimes it completes with an error (see below). The "Resolution" field is not used by the rule at all, so why is it complaining about it?

The audit log has this in it:

Action details:

Issue condition

The following issues passed:

EKM-5064

Transition issue

Unknown fields set during transition. Field may not be on transition screen. Fields ignored -

Resolution (resolution)

Transitioned issues to

Closed

Accepted answers

Sean Kubin

Instead of transitioning the issue and setting the resolution in one action, try splitting them.

So, transition the issue, then create a new action to update the resolution.

For example:

All comments

Clark Everson

How is the automation set? And are their workflow triggers that set fields?

I would check the automation and possibly share that as well.

the only other place based on what I see is the workflow itself. This automation seems to trigger a transition change to closed. It appears that resolution is set to do something(which it should do something). You should make sure the resolution is still being set.

if that isn’t it I think we need more information though.

Ravi Sagar _Sparxsys_

Hi @phil.americus

The error seems to be indicating towards an issue with the transition screen.

As suggested by @Clark Everson check your workflow transition's post function, check if some field values as set and are those values there in the transition screen or do you even have a transition screen?

Ravi

phil.americus

@Clark Everson , @Ravi Sagar _Sparxsys_

Here's the post functions that I have:

To state X:

The following will be processed after the transition occurs

The Assignee of the issue will be set to Phil Americus.
Set issue status to the linked status of the destination workflow step.
Add a comment to an issue if one is entered during a transition.
Update change history for an issue and store the issue in the database.
Re-index an issue to keep indexes in sync with the database.
Fire a Generic Event event that can be processed by the listeners.

From X to Closed:

The following will be processed after the transition occurs

Set issue status to the linked status of the destination workflow step.
Add a comment to an issue if one is entered during a transition.
Update change history for an issue and store the issue in the database.
Re-index an issue to keep indexes in sync with the database.
Fire a Issue Closed event that can be processed by the listeners.

The "Resolution" field never gets set.

There is one transition screen that sets the Resolution when moving to the Resolved state. Even when setting the state to Resolved and then to X, I also get the same error.

Clark Everson

Are you trying to set the resolution from the workflow or from the automation? Whichever one you did maybe also try doing the other. If in the automation that you haven’t done it for have that be the first action to complete

Robert Horan

@phil.americus - was this resolved? I'm curious to know what happened.

phil.americus

@Robert Horan Hi. Since it happens infrequently, I haven't had the time to look into it any deeper, I just delete those emails.

Jonathan Le_5mx1f6

@Robert Horan @phil.americus We have two different processes at work. The error is coming from the Automation and not a Post Function of a workflow transition.

Also, Jira built-in System Events states

Issue closed : An issue has been closed. (Note that an issue may be closed without being resolved)

If we can assume...

Automation fires first
The error is more cryptic than it appears and that it logs this error because it can not successfully change the resolution to Resolved because it is already Resolved.
The order of the Automation Transition issues are not in order of the execution logic

Then perhaps this is what's going on.

Issue status is set to X.
Automation saw that X was set.
Automation transitions the issue to Closed.
1. Transition to Closed sets the resolution to Resolved
Automation attempts to sets the resolution to Resolved, but fails.

The solution could be...

add a post function to your transition so that the resolution is set to Done since we know that the system event Issue closed doesn't add a resolve.

Remove the resolution from the Automation Transition Issue and rely on the Transition to Closed post functions to set your resolve.

I am of the belief that the System Events are apart of the Legacy Automations that Jira says they want to deprecate. Also, my apologies is not written as a 1:1 to the fore mentioned use-case. Solution bullet #1 may be all that you need to do.

Robert Horan

I'm 99% sure this is the problem:

Capture 2021-05-07 at 18.29.07.png

Jonathan Le_5mx1f6

Agreed, rather than not defining a resolution as my last image shows you should deselect Resolution from the option "Choose fields to set..."

Robert Horan

Hi @phil.americus

Have you tried deselecting this?

phil.americus

@Robert Horan I have been getting less errors from the automation recently. I just checked the last error and got this:

I get "Destination status could not be resolved".

Guillermo_ou2neq

This worked for me. Thanks!

Robert Horan

@phil.americus Sorry for the delay in responding! I didn't see this until now. Destination status could not be resolved sounds like there is no transition available.

Olive Sun

Has this been resolved? I just met the same issue. The following error message displayed:

"Unknown fields set during transition. Field may not be on transition screen. Fields ignored -Resolution (resolution)"

I checked 1) the Workflow Post Function never set the resolution value, 2) Not select resolution in Automation.

Sean Kubin

Instead of transitioning the issue and setting the resolution in one action, try splitting them.

So, transition the issue, then create a new action to update the resolution.

For example:

Flavien Gache

This solved my issue, and your answer was not even accepted.

I corrected this mistake. Thanks for the tip. Automation seems to hate when you change the Resolution on a transition block. I don't know why though.

Sankalp Chugh

@Olive Sun

I fixed that issue by setting a transition screen (I used Transition: Comment Only) for that transition.

Sankalp

Rex Parsons

Yes, this fixed the problem I was having. Once I unselected the resolution, it worked without error. Thanks.

Spencer Hudson

A bit of an update in 2026 on this issue. The problem is the same one , but the dialogue box has changed and the steps for the solution.

Your still looking to remove the "resolved" element ... in the screenshot below i've opened up the "more options" and removed the offending code.

Screenshot 2026-09-10 100319.png

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-service-desk-cloud

automation

jira-service-management