Release Notes
Apr 7 2025: Add support for threaded comments to keep the hierarchy
Mar 18 2025: Add support for the JSM fields
Request ParticipantsandOrganizationto the Field EditorMar 13 2025: Add support for cloning to issue types which require setting the
Sprintfield at issue creation timeMar 11 2025: Fix an issue with Team Managed project clones to properly reference fields within the newly created rules
Feb 10 2025: Add support for DE region
Jan 31 2025: Support creating new values for labels, components, versions and select custom fields in the Field Editor
Jan 14 2025: Add project and issue type selection dialog in the Field Editor when adding a field with multiple contexts
Jan 13 2025: Add support for the Team field to the Field Editor
Dec 19 2024: Fix an issue when cloning subtasks of an archived project
Dec 18 2024: Ensure that very long issue descriptions (approaching Jira's allowed limit) are cloned in their entirety
Dec 16 2024: Fix an issue when editing the parent field in Field Editor and using “Create and Confirm”, which would ignore the parent value from the Field Editor
Dec 5 2024: Fix an issue where users could not select all values from the dropdown in the Field Editor
Dec 3 2024: Properly handle Workflow required validators for the assignee field
Dec 2 2024: Add support for cloning Jira Service Management forms
Nov 25 2024: Add Feature Hub page and update sidebar menu. Move Bulk & Project clone buttons from sidebar to Feature Hub
Nov 7 2024: Ignore Forge read-only fields when cloning issues
Oct 11 2024: Enable exporting cloned issue keys as a CSV file
Jul 18 2024: Add support for the parent field to the Field Editor
Jul 15 2024: Add support for cloning Jira Work Management Category field to Project Clone
Jun 17 2024: Add option to Disable Logging
May 27 2024: Fix an issue when cloning projects with JWM approvals in custom statuses, where the cloned workflow could no longer be edited
Apr 11 2024: Add support for cloning projects to another instance
Mar 7 2024: Improve loading time of “Manage Presets” and “Post Function Clone” pages for Jira instances with a large amount of projects
Jan 29 2024: Move Direct Link URL to Getting Started page
Jan 18 2024: Support for separate Epic/Tree Post Function
Dec 29 2023: Only allow hierarchy level 0 issue types for target issue type in Epic/Tree Clone
Dec 22 2023: Support cloneMultipleTimesIndex variable when editing fields with Jira Expressions
Dec 18 2023: Add Advanced Scheme Options for cloning company-managed projects
Nov 16 2023: Show placeholders while Deep Clone uploads attachments
Nov 9 2023: Team field will now be cloned while cloning across instances
Oct 26 2023: Advanced Bulk Edit now supports custom fields created by third-party apps
Sep 07 2023: Project Clone can now be accessed directly from the Deep Clone navigation
Aug 31 2023: Support adding Epic/Tree clone presets as an action to issue menu
Aug 29 2023: Project Clone now also clones the Notification Email setting
Aug 24 2023: Add support for presets in Bulk and Epic/Tree clone
Aug 17 2023: Improve loading speed of Single Clone dialog when the project contains many issue types
Jul 24 2023: The preview counts of cloned versions, attachments, comments, issue links, votes, watchers and work logs are now updated immediately when changing the selected issues.
Jul 19 2023: Fix an issue where text fields with very advanced and specific formatting were incorrectly cloned
Jul 17 2023: Ignore subtasks that are not being cloned when checking for missing required fields.
Jun 30 2023: Compatibility with Jira’s “dark theme”
May 8 2023: The Deep Clone “Restrict access” settings are now cloned as well when cloning a project if the source project had user groups with restricted access configured
Mar 22 2023: Add a mechanism slowing down the clone process when the Jira instance is under heavy load and unable to process as many requests as usual
Mar 14 2023: Add improvements to the user experience when using presets in Single Clone
Mar 8 2023: Ensure that the test location is preserved when cloning Xray test details, even if the corresponding folder doesn’t already exist in the target test repository
Jan 2 2023: Auto-select the “Same as original” issue type and subtask issue type in Bulk and Epic Clone
Jan 2 2023: Add “Cancel”, “Pause” and “Back” buttons to Single Clone progress dialog (previously only available in Bulk/Epic Clone)
Dec 1 2022: Cloning issues multiple times is now available for Bulk, Epic/Tree Clone and Workflow Post-Functions clone
Oct 31 2022: Clone jobs can now “Run in the background”. The Clone History shows finished and running clone jobs
Oct 26 2022: New Epic/Parent link clone option “Link to cloned parent, or else keep original”, can be used to clone e.g. an Epic within an Initiative
Sep 7 2022: The issue restriction field used in team-managed projects is now cloned as well
Jul 6 2022: Add support for Jira expressions in the Field Editor
Jun 20 2022: Add support for instance clone between instances in different data residency locations
May 25 2022: Enable cloning Xray “Gherkin” (Cucumber) and “Unstructured” (Generic) test details. Xray tests are now cloned to the same folder as the original tests in the Xray Test Repository
Apr 28 2022: Add a warning to the clone dialog if required project permissions are missing
Apr 19 2022: Add support for cloning manual test steps created with Xray Test Management
Mar 30 2022: Fix an issue when cloning custom fields from a team-managed to a company-managed project, where Deep Clone would sometimes not set the correct field value even if the fields had the same name as documented here
Jan 13 2022: Show detailed progress while cloning a project
Jan 5 2022: Add “currentUser()” to the Assignee and Reporter fields in the Field Editor, which allows to set the user triggering a preset or post-function to be set as the Assignee or Reporter
Nov 10 2021: Add “Back” and “Pause” buttons to Clone progress dialog
Nov 9 2021: Fix an issue with Instance Clone that would sometimes use incorrect values for ID-based fields (e.g. components or versions)
Oct 15 2021: Jira Automation can now be triggered from Deep Clone using an Incoming Webhook
Sep 30 2021: The JSM "Request Type” field can now be cloned when using “Immediately clone issue” and if the issue type stays the same
Sep 1 2021: Create Bulk Clone shortcuts within your Jira projects
Jul 13 2021: Increase the maximum number of issues supported in Bulk Clone from 5,000 to 100,000
Jun 14 2021: Allow managing access to “Project Clone” using a global permission
May 5 2021: Fix an issue with Epic/Parent links in Bulk Clone if Advanced Roadmaps is used
Apr 20 2021: Improve loading time of "Single Clone" dialog
Mar 10 2021: Harmonize the Field Editor between Single Clone and Bulk Clone
Mar 3 2021: Simplify choosing subtasks, add new option to clone only selected subtasks in Bulk Clone
Feb 22 2021: Adjust Bulk Clone order so Stories are immediately cloned after the respective Epics
Feb 4 2021: Make lesser used “Clone fields” and “Advanced options” expandable
Feb 2 2021: New option "Create a new sprint with identical name" when cloning the Sprint
Jan 14 2021: Fix post-function clones triggering themselves, leading to endless cloning loops
Nov 24 2020: Clone Jira projects, including components, versions, settings and issues
Oct 26 2020: Preserve sort order when cloning subtasks
Oct 26 2020: Support Epic Link as required field
Sep 30 2020: Support Epic Link and cloning an issue multiple times in Presets
Sep 29 2020: Fix prefix summary and components/versions when using “Create and “confirm”
Sep 25 2020: Auto-edit fields in Presets
Sep 14 2020: Auto-edit fields when using Deep Clone in post-functions
Aug 20 2020: The new “Manage Presets” screen simplifies creating and managing Presets
Aug 6 2020: Provide option to clone a single issue multiple times
Jul 17 2020: Allow creating non-existing versions and components when cloning across projects
Jul 9 2020: Show warning if project is misconfigured with hidden required fields
Apr 22 2020: Allow cloning Epic Link for Deep Clone post-functions
Apr 20 2020: Notify the creator of a Deep Clone post-function if there are any errors when the post-function is running
Apr 14 2020: Allow restricting access to the clone fields “attachments”, “comments” or “work logs”
Jan 14 2020: Epic Links can now also be used with Bulk edit
Dec 3 2019: Support next-gen Epic Clone with “Create and confirm”
Nov 11 2019: Show which required fields are missing before cloning
Oct 17 2019: Offer a delay before starting a post-function in case other post-functions should run before Deep Clone
Sep 20 2019: The user starting Deep Clone no longer gets added to every cloned issue as a watcher
Aug 22 2019: Respect required fields defined in workflows
Jul 29 2019: Filter subtasks to be cloned using JQL
Jul 4 2019: Support cloning Initiatives and arbitrary issue hierarchies using Jira Portfolio
Jun 18 2019: Support Epic Clone for next-gen projects
May 7 2019: Introduce triggering Deep Clone using workflow post-functions
Apr 24 2019: Allow using “Same as original” project or issue type for Presets
Jan 18 2019: Introduce new Bulk Clone button supporting to clone more than 1000 issues
Jan 9 2019: Offer “Same as original” project for Bulk Clone
Dec 4 2018: New options for issue links to link to the cloned issues
Sep 14 2018: Allow ranking cloned issues in the order of the original issues after Bulk Clone
Jun 18 2018: Epic Link can now also be cloned using Bulk Clone
May 23 2018: Allow to “Restrict access” for Deep Clone to specific projects
Mar 28 2018: Allow cloning all subtasks along with a single issue
Feb 27 2018: Initial release, including Single Clone with “Clone immediately” and “Create and confirm” options, clone attachments, comments, issue links, voters, watchers and work logs