• codefortynine
  • Go to codefortynine.com
  1. Deep Clone for Jira
  2. Release Notes

Release Notes

  • 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

  • Mar 21 2022: Support cloning issues between two projects using different story points/estimation fields

  • Feb 9 2022: Enable data residency for Deep Clone for Jira

  • 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

  • Dec 14 2021: Cloning issues between Jira cloud instances is now supported by Single Clone, Epic/Tree Clone and Workflow Post-Functions Clone

  • 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

  • Jul 12 2021: Deep Clone is one of the first apps to join the Atlassian “Cloud Fortified” program, offering advanced security, reliability and support

  • 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

  • Apr 15 2021: Clone issues between Jira cloud instances

  • 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

  • Dec 23 2020: Add presets as an action to the issue menu

  • Dec 15 2020: Project Clone is now available on the REST API

  • 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

  • Jan 7 2020: “Bulk edit” introduced for Bulk clone

  • 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

  • Sep 4 2019: Allow cloning the issue status

  • Aug 22 2019: Respect required fields defined in workflows

  • Aug 21 2019: Introduce global permission for Bulk Clone

  • 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

  • May 4 2018: Introduce Epic Clone

  • Apr 15 2018: Introduce Bulk Clone up to 1000 issues

  • Mar 28 2018: Allow cloning all subtasks along with a single issue

  • Mar 19 2018: Introduce Presets

  • 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

Deep Clone for Jira Logo
Privacy Policy / Atlassian Marketplace
Copyright © 2023 • Powered by Scroll Viewport & Atlassian Confluence
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.

Contact Support Close