Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation rule execution failed

Jack Zhao
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!
August 7, 2025
I have an automation rule that automatically adds the specified members to the "Request Participants" field when a ticket is created.
 
I set myself as the owner and "Automation for Jira" as the actor, but the rule ultimately fails with the following error log:
"√ Work item created 08/07/2025, 15:48:37
 
! Edit work item 08/07/2025, 15:48:38
Edited work item successfully, however, some of the set fields aren't available. Fields ignored: Request participants (customfield_10039)"
image.pngimage.png

4 answers

0 votes
Pedro Olmo
Contributor
August 7, 2025

Hello @Jack Zhao ,

 

You need add request participant field in workitem screens

 

regards

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 7, 2025

Hi @Jack Zhao -- Welcome to the Atlassian Community!

There are several possible causes for this symptom, and here are some things to check:

#1) The Work Item Created trigger has a known racetrack timing defect where the rule can start before all data is available, or the work item is in a stable condition.  This can cause weird rule errors and unexpected behavior.  The Atlassian team knows about this problem and is working on architectural changes to address it, although there is no timeline for the fix.

Until the fix happens, I recommend mitigating the problem by always adding the Re-fetch Work Item Data action immediately after this specific trigger.  That will slow the rule slightly and reload data before the steps proceed.

 

#2) The rule may be scoped such that the field cannot be changed.  Thus, it must be a rule for a JSM project scope.

 

#3) As @Marc - Devoteam notes, if the field has been removed from views, often automation rules cannot change it.

 

#4) An unlikely case is when someone has created a custom field with the same name, leading to confusion in the rule as to which field to change.  Please check with your admin if there are multiple fields with that name.

 

#5) The rule has become corrupted and so cannot work as expected.  To check for this, disable your rule and re-created it from scratch, testing the new rule.

 

Kind regards,
Bill

0 votes
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 7, 2025

Hi @Jack Zhao 

Welcome to the community.

This error represents that the field "Request Participants" is not on the create or edit screen of the work item type used by the request type.

Can you verify this.

0 votes
Nikola Perisic
Community Champion
August 7, 2025

Welcome @Jack Zhao 

What is your set up for the Request Participant?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events