RFC-145: New asynchronous bulk mutation APIs for Jira Cloud REST API

We are introducing RFC-145, which proposes a new set of asynchronous bulk mutation APIs for the Jira Cloud REST API. These APIs are designed to handle large-scale data operations more efficiently by processing requests asynchronously, reducing the risk of timeouts and improving overall system stability for high-volume updates.

What's changing The proposed RFC introduces a consistent pattern for bulk mutation operations in Jira Cloud:

• Asynchronous processing: Instead of waiting for a synchronous response, you will receive a job ID to track the progress of your bulk request.
• New bulk endpoints: The RFC covers asynchronous versions of common mutation tasks, such as bulk issue updates and deletions.
• Status polling: A new set of endpoints will allow you to poll for the status of an ongoing bulk job and retrieve the final results once completed.

What you need to do This is currently an RFC (Request for Comments) and is open for feedback from the developer community.

1. Review the full proposal on the [Atlassian Developer Community] (https://community.developer.atlassian.com/t/rfc-145-jira-cloud-rest-api-async-bulk-mutation-apis/102577).
2. Provide your feedback, use cases, or concerns directly in the community post to help shape the final implementation.
3. Stay tuned for further updates regarding the Early Access Program (EAP) and official rollout dates.