Problem

• Automation rules in Jira can currently update only up to 50 Assets objects in an Assets custom field at a time.
• When more than 50 objects are present, the automation rule does not update objects beyond the first 50, even though the same field can be updated manually with more than 50 objects without any issue.
• This limitation breaks consistency between manual editing and automation-driven updates and blocks use cases that rely on larger object sets.

Current Behavior

• An automation rule uses an Assets/JSM field that can contain multiple Assets objects (e.g., people, devices, configuration items, etc.).

• When the rule runs, it calls the Jira Assets endpoint:

• • POST /query/evaluate

• • with parameters: start=0, limit=100

• However, Jira enforces a default internal max limit of 50, so:

• • The request is effectively capped at 50 objects.

• • Only the first 50 objects returned by the query are updated in the Assets custom field.

• If the field contains more than 50 objects:

• • Objects beyond the 50th are not updated by the automation rule.

• In contrast, when editing the same Assets custom field manually on the issue view:

• • Users can select and save more than 50 objects successfully.

• • No such cap is applied to the manual operation.

Expected Behavior

• Automation rules should be able to update all matching Assets objects in the Assets custom field, without being limited to 50.

• Specifically:

• • The automation rule should either:

• • • Respect the requested limit (e.g., up to 100 or more), or

• • • Transparently handle pagination (multiple calls) to fetch and update all required objects.

• From an end-user/admin perspective:

• • The behavior of automation should be consistent with manual updates to the Assets field.

• • If a user can manually set, say, 200 objects in the Assets custom field, an automation rule targeting the same field and objects should be able to do the same.