Announcing the Enhanced Bulk Move API: Move parent and child issues in one request!

[#1]

Hi Atlassian Community!

We’ve heard your feedback and are excited to unveil our latest enhancement to the Bulk move issues API. This update makes it easier to move issues across projects and work types, and marks an important step in modernising the bulk move functionality to provide you with a more streamlined experience.

Whats changing?

Previously, the Bulk move issues API was limited to moving issues of a single work type from one project to a single work type in another (or the same) project. Additionally, it did not support setting an epic for standard issues in a request. While this was sufficient for simple migrations, it complicated the process of moving large volumes of issues, especially those spanning multiple types and projects, requiring numerous API calls.

With our latest update, the Bulk move issues API addresses these problems. You can now move multiple issues of different work types from various projects into a single work type in a new or existing project, all in a single request. Furthermore, you can now assign an epic to standard issues during a bulk move by specifying the target epic as their parent in your request.

These enhancements significantly reduce the number of API calls required for complex migrations and streamlines the process of moving epics and their child issues to a new project. Ultimately, this update delivers a faster, more efficient bulk move experience for teams managing large-scale changes.

How do I know if my use case is supported?

Previously supported and continued support:

• Moving issues of one work type from one source project to a target project and work type in a single request.

• Moving a parent issue of a standard work type A, with its multiple subtasks, in one project to an issue of a standard work type B in the same project or a different project.

Newly supported

• Moving parent issues of multiple standard work types from multiple source projects to a target project and standard work types in a single request.

• Setting a target parent for issues, while preserving issue hierarchy, during a move request.

We’d love to hear from you

If you’re interested in shaping the future of bulk operations in Jira or would like to suggest improvements so Jira is better for you and your team, we’d love to hear from you.

Book a time to chat with the team 🗓️ or drop your feedback below. We’re excited to hear what you think!

Documentation and further info

Bulk Operation APIs: Additional Examples and FAQs

What are work types? | Atlassian Support

Bulk move issues API

[prudhvi jira]

Great update! Happy to hear that now we can bulk move within a single request, making it a very easy process. It's very useful for post-migration activities and moving all issues in a single request.

[Lumina Gajanayake]

Hi Prudhvi,

Thank you for your positive feedback! We're excited for your team to try out the API, and we hope that this update enhances your experience with Jira.

Best regards, 

Lumina