How to use
- Enter your site (your-team.atlassian.net), email and an Atlassian API token, then press Connect.
- Find source issues with JQL or paste issue keys or links. Results are all selected.
- Pick the target project and issue type, tick what to copy (turn on Whole tree for epics), and preview the tree.
- Press Validate to see the dry run, then Run clone and copy the new keys.
Jira’s built-in clone copies one issue at a time and leaves the epic’s children behind. TreeClone walks the tree instead: with Whole tree on it follows both team-managed parent links and the classic Epic Link field, up to six levels deep, and recreates every child under its new parent. Each issue is visited once, so loops cannot run forever.
Before each create, the target project’s create screen (createmeta) is read and only fields that exist there are sent, converted to the right format: options, priorities, users, versions, components and custom fields. Required fields that would stay empty stop that issue before it is created instead of failing halfway. Components are skipped when the target is a different project because their IDs differ.
Optional steps copy comments in their original rich format, re-upload attachments, recreate issue links in the same direction, and move the new issue to the source status when the target workflow has a direct transition to it. Every clone gets a “Cloned from” comment. Browsers cannot call Jira directly because of CORS, so requests pass through a small relay that forwards them as-is; it has a shared daily limit. TreeClone is not affiliated with or endorsed by Atlassian.