Cloneyard for Jira: documentation
Source for the public knowledge base at https://greatwork.company/apps/cloneyard.
Where to find it
- Apps > Cloneyard: bulk clone from a JQL search, clone one work item and everything under it, or copy a whole project's contents. Tabs: New clone, My jobs, Presets.
- On a work item: ... > Clone with Cloneyard: clone that work item (and, by default, everything under it).
- Jira settings > Apps > Cloneyard (Jira admins): who may use it, limits, every job, audit log.
Clone in three steps
- Pick what to clone. A JQL search, one work item key, or a project. "Include everything under them" adds children at every level: stories and tasks under epics, sub-tasks, and work items under custom levels such as initiatives.
- Pick where. The same project as each original, or another project. For a project copy, create the target project first with Jira's Create project.
- Preview, then Clone. The preview lists how many work items at each level, which issue type each becomes, fields that won't fit the target, what will be created (versions, components, sprints), and any permission you're missing. Change the type mapping and preview again if needed. Nothing is created until you press Clone.
Options
| Option | What it does |
|---|---|
| Attachments | Copies files up to the admin's limit (default 25 MB). Larger files are listed in the job notes |
| Comments | Copies comments in order; each starts with "Name commented on date (copied from KEY)" |
| Status | Moves each clone to its original's status when the target workflow has it; otherwise to the closest status in the same category, and notes it |
| "Clones" link | Links each clone to its original, like Jira's own Clone |
| Issue links | None; between the cloned work items (pointed at the clones); or all (outside work items stay linked too) |
| Sprints | Leave out; same sprint as the original (open sprints); or copy the sprints to a board in the target with goals and dates. "Also copy closed sprints" replays them (needs a board with no active sprint) |
| Versions, components | Match by name in the target; match and create the missing ones (another project only, needs Administer projects); or leave empty |
| Reporter, assignee | You or the original reporter; keep, clear or set the assignee to you |
| Find and replace, prefix, suffix | Applied to every clone's summary, children included |
| Shift dates | Moves due dates, start dates, custom date fields, version dates and sprint dates by N days |
| Add labels | Added to every clone |
| Create a board | Project copy only: a board of the same type with the filter pointed at the target. Columns are listed in the notes to set by hand |
How fields are matched
- Same field in both projects: copied as is (select options matched by name, versions and components by name, priorities by name).
- Team-managed projects have their own fields: matched by name and type, so "Story Points" fills "Story point estimate".
- Fields that are not on the target's create screen are set right after creation if they are on its edit screen. Anything else is listed in the preview and the job notes with examples.
- Never copied: status history, worklogs, votes, watchers, Rank (clones keep the original order), and fields Jira computes.
Jobs
- Jobs run in the background; you can close the page. My jobs shows progress.
- Stop finishes the current work item and stops. Resume continues a stopped job.
- Retry failed issues re-runs only the work items that failed (for example after you add a missing option or permission). Finished clones are not touched.
- Original to clone CSV lists every original, its clone and the result.
- Find all clones of a work item with JQL:
cloneyardSourceKey = KEY-1.
Undo
Undo this clone deletes every clone from the job (children first), then the versions, components and sprints the job created if nothing else uses them. "Keep clones someone changed after the clone finished" is on by default. Undo is available for 30 days, to the person who ran the job and Jira admins, and needs the Delete work items permission in the target.
Presets
Save a setup under a name; share it to make it available to everyone on the site. Use it from the Presets tab, adjust, preview, clone.
Permissions
You clone only work items you can browse, into projects where you can create work items. The preview checks the other permissions your options need in each target project. Jira admins can limit Cloneyard to groups (admin page). Clones are created by the Cloneyard app user, so Jira shows the app as creator.
Limits
Up to 5,000 work items per job (admin setting, default 2,000). The target project must exist. Workflows, screens, schemes and board columns are not copied. No copying between Jira sites.