Cloning Jira work items between Cloud sites — with Xray links intact
For years the hard boundary in Jira cloning hasn't been volume, it's been the site edge. A client's site, an acquired company's site, a production site you don't share credentials with. Our own app stopped there too until recently.
We've just shipped cross-site cloning in Bulk Clone Professional for Jira (Advanced edition, now at 6.1). A few of the design decisions came from questions asked in this community, so sharing how it works:
- Pick another Jira Cloud site as the destination. Subtasks, attachments, comments, links and people come along; source and clone link back to each other.
- Atlassian sign-in, no API tokens. An admin connects the site once; after that everyone clones as themselves, with their own permissions on both sides.
- Fields, options and users map to their counterparts on the target site. Xray tests keep their steps and stay in their Sets, Plans and Executions.
- Runs from Automation rules or a workflow post function.
Every user then picks the site as a destination and clones with their own permissions.
Also recent, in Standard
Clone speed: from one at a time up to fifty in parallel, with large runs auto-throttled to stay inside Jira rate limits.
Still a Forge app
Runs on Atlassian infrastructure, data-resident, Cloud Fortified. The one external call is to Xray's API when you use Xray features. And as of this month it's available on Atlassian Government Cloud too, with the full Standard feature set.
Happy to answer questions here — especially from anyone mid-migration from Data Center who's dealing with multi-site setups.
Docs:
https://bulkclone-support.atlassian.net/wiki/spaces/BCP/overview
2-minute demo:
Marketplace:
https://marketplace.atlassian.com/apps/1213028/bulk-clone-professional-for-jira?hosting=cloud
Lars Brodén
Product Manager, LB Consulting Group · Silver Marketplace Partner
