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 rule execution failed

Jack Zhao

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)"

Accepted answers

All comments

Nikola Perisic

Welcome @Jack Zhao

What is your set up for the Request Participant?

Marc -Devoteam-

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.

Bill Sheboy

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

Pedro Olmo_7tm5vp

Hello @Jack Zhao ,

You need add request participant field in workitem screens

regards

Jack Zhao

I am using the default configuration

Jack Zhao

@Pedro Olmo I'm using the default configuration, which includes the "request participant" field.
Is this related to the default configuration? Previously, this field was in the "Hidden when empty fields" section, and I've since changed its location. I haven't had a chance to try it yet; I'll have to wait until the next ticket is created.

Jack Zhao

Thanks @Bill Sheboy

I'll check them one by one.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management

cloud-automation