Bulk fetch issues now supports up to 1000 issues per request

The Bulk fetch issues API (POST /rest/api/3/issue/bulkfetch) now supports a maximum of 1000 issues in a single request, up from the previous limit of 100. This higher limit is available for requests optimized for efficient processing. https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/1-000-Issues-One-Call-Bulk-Fetch-Gets-a-10-Boost/ba-p/3281867

What's changing To qualify for the 1000-issue limit, your request must meet the following criteria:

• Explicit field selection: You must explicitly name at least one field to include. Wildcards like *all or *navigable, and requests containing only exclusions (e.g., -description), are not eligible.
• Field count: No more than 100 fields can be explicitly included.
• Single-value fields only: Included fields must not return multiple values (e.g., comment, worklog, or attachment are excluded).
• Restricted expands: The expand parameter must not include changelog, editmeta, operations, renderedFields, transitions, or versionedRepresentations.

What you need to do No action is required if you wish to continue using the existing 100-issue limit. To take advantage of the 1000-issue capacity:

• Update your request payload to explicitly list the specific fields you need.
• Remove any multi-value fields or restricted expand parameters.
• Increase your batch size up to 1000 issueIdsOrKeys.

If you require multi-valued data or changelogs for a large set of issues, we recommend splitting the work: use one 1000-issue call for "cheap" fields and separate, narrower calls for complex data. For changelogs, use the Bulk fetch changelogs endpoint to avoid the 40-item cap imposed by expand=changelog.

For more details, see the Bulk fetch issues reference documentation.