-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
Component/s: Request type - APIs
-
1
-
Minor
-
4
Issue Summary
A Jira Service Management (JSM) automation rule that creates multiple work items (requests) using the "Create work item with a request type" action intermittently fails with below error.
The set fields may be unavailable for this space/type. Fields ignored: summary Error creating request The request type associated with this email account has validation rules applied to one of the fields. You can either create a new request type for this email account or remove validation from the field.
This issue is sporadic; in a single automation execution looping through multiple items, most requests are created successfully while only a few fail, despite using the exact same request type and configuration.
Steps to Reproduce
- Create a JSM automation rule (e.g., triggered by a scheduled search or an Asset-related trigger).
- Add a "For each" loop or multiple actions to create work items.
- Use the "Create work item with a request type" action.
- Select a fixed Request Type where the "Summary" field is visible and required on the portal form.
- Execute the rule multiple times or with a large number of iterations in a single run.
Expected Results
All work items are created successfully as long as the Summary value is provided and the request type configuration is correct.
Actual Results
The action intermittently fails with a above error. Audit logs show the Summary field was "ignored" because it was deemed "unavailable" for the request type at that specific moment of execution in backend process.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available