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

Dinesh Kumar Saminathan
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 26, 2024

could you give the solution for this question

1 answer

0 votes
Jerrold - Empyra
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 26, 2024

Hi @Dinesh Kumar Saminathan 

Can you please share the screen shot of the automation rule and audit log it will be helpful to identify the root cause. 

Thank you. 

Dinesh Kumar Saminathan
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 26, 2024

Capture.PNG

Jerrold - Empyra
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 26, 2024

Hi @Dinesh Kumar Saminathan 

Thanks for sharing the audit log.

I believe that you have selected the resolution field in the transition issue action under "choose fields to set".

So, what's happening is when setting fields in the same action, specifically in the transition issue action, it will tend to change the resolution while transitioning the issue.

Therefore, we need to have a transition issue screen where the resolution field should be present.

To avoid this, remove the resolution field from the transition issue action and add another action - edit issue action - where you can set the resolution field.

Additionally, I believe you also have some validators or conditions in your workflow; as, in order to move an issue to a certain status, you must update Launch Darkly value. For that as well, you need to set an action.

 

Thank you.

Suggest an answer

Log in or Sign up to answer