Atlassian (Jira) changed its API changelog

===================================================================
--- before
+++ after
@@ -36,9 +36,9 @@
 News and Updates
 Get support
 Sign in
 
-Last updated Aug 26, 2026
+Last updated Aug 28, 2026
 
 CHANGELOG
 
 This page includes release notes and updates for Jira Cloud app developers. Use this page to keep track of upcoming changes, deprecation notices, new features, and feature updates from Jira Cloud Platform.
@@ -50,8 +50,38 @@
 Go to our developer community to ask questions. You may also be interested in the What's New blog for Atlassian Cloud where details of major changes that affect all users of the Jira Cloud products are announced.
 
 Filter types
 
+28 AUGUST 2026
+
+ADDED 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.
+
 26 AUGUST 2026
 
 ADDED GLOBAL STATUSES ARE NOW AVAILABLE IN TEAM-MANAGED WORKFLOWS
 
@@ -311,26 +341,8 @@
 ADDED THE WORKFLOW SEARCH API NOW LETS YOU FILTER BY PROJECTID
 
 The Workflow Search API now supports a new optional projectId query parameter. When provided, the search returns only the workflows used by that project. You can combine it with the existing scope parameter, but the project must belong to the same scope you specify - otherwise no workflows are returned.
 
-18 JUNE 2026
-
-ANNOUNCEMENT PARTNER SECURITY INCIDENT RESPONSE PROGRAM
-
-We've introduced a structured process for partners and Atlassian to jointly investigate security incidents affecting your app or the customer data it handles.
-
-What's changing
-
- * Log sharing for Forge apps: Atlassian can now share incident-scoped platform logs and app telemetry with you during an investigation. This provides the data you need to diagnose and resolve issues faster.
-
- * A single reporting path: You can now report security incidents through the new developer support portal form. This form serves as the shared record for both you and Atlassian.
-
-What you need to do
-
- * Review the program overview page to understand eligibility and support levels.
-
- * Ensure your security contact information is up to date in the partner account to ensure you are ready before an incident occurs.
-
 Rate this page:
 
 Unusable
 Poor