Deep Clone for Jira is free for up to 10 users and offers a 30 day free trial. let me know if this works for you. You could give Deep Clone for Jira a try. Some example apps are below. You can also maintain links/dependencies while cloning. App Permissions (Project Permissions) Deep Clone for Jira has to be granted specific project permissions to properly clone issues. With this tool at their disposal, Jira. This can also be automated using a Deep Clone’s post function on a transition. Since "Deep Clone For Jira" from Marketplace Atlassian comes with the pricing, I tried to achieve deep cloning of an Epic via automation. Now use this story and its sub tasks as a template to create other stories. Free for up to 10 users ; Bulk Clone issues in Jira; Clone Jira projects; Clone epics and larger issue layers in Portfolio ; Clone and move issues to another project or issue type ; Migrate issues to another instanceWhen Deep Clone creates an issue in your instance, the issue key is generated just as if a Jira user creates an issue manually. Clone and move. Deep Clone for Jira add-on is an advanced solution for cloning single issues, a bulk of issues, epics, or template projects in Jira. . Deep Clone for Jira is a Cloud only advanced cloning app that lets users go far beyond Jira’s native cloning functionality. (Update 2022-01-27: Deep Clone for Jira is free for instances with up to 10 users. When cloning Jira Issues - your checklist data would be cloned along with the custom field 🎉. The Confluence/external link will be copied along with the JIRA issue link. That means that the issue is linked to the same sprint. Deep Clone is the most powerful cloning app for Jira cloud. So, you can update the filter to allow to see those Epic and task. The process would look like this:If your use case is not possible with Jira Automation, you can also have a look at our Jira cloud app Deep Clone for Jira. I've seen the Deep Cloning add-on mentioned, and also the cloneProject command from the Bob Swift CLI add-on. After deep diving we found out that issue keys for cloned projects are not matching with original issue. If you want to clone the issue status "done" but it is not possible to transition from "open" to "done", Deep Clone is not able to clone the issue status. Instance Clone. Gain efficiency when a project needs are repetitive. Option 2: Project Clone from the Bulk Clone dialog . Browse the top apps, add-ons, plugins & integrations for Jira, Confluence, Bitbucket, Hipchat & other Atlassian products. A short tutorial about cloning a single issue with presets with our cloud app Deep Clone for Jira. You can find a list of apps that clone issues at the link below, but I can verify that with our app Deep Clone for Jira you can clone comments and other clone comments and other advanced content by applying the following steps. Since we create new issues and do not delete data, nothing can be lost during the test. Due to API limitations in Jira, this action does not clone issue links and comments. Deep Clone for Jira Operational 90 days ago 100. Or it could be done when the issue in that project transitions to Y (assuming. 99 per month for each user up to 100 total; 13. 7k installs. Edit the Summary. Turn on suggestions. Filter for all issues in this sprint using the Jira issue search. Free for up to 10 users ; Bulk Clone issues in Jira; Clone Jira projects; Clone epics and larger issue layers in Portfolio ; Clone and move issues to another project or issue type ; Migrate issues to another instanceAction: Clone issue-Project: Destination project-Issue Type: Destination issue type-Summary: Destination summary-Fields set: Fields you wish to populate. Thank you for mentioning Deep Clone for Jira, @Ismael Jimoh . Advanced cloning of single issues, issue hierarchies, a bulk of issues or entire projects in Jira. External Data. Copy the original workflow scheme, make the change, then associate the workflow scheme project by project. Select "Epic Clone" and configure your clone. Deep Clone for Jira is the most powerful. After you've installed Deep Clone to your instance, you simply: Navigate to the issue you want to clone multiple times; Click on the three dots menu on the top right; Click Deep Clone; Configure your clone (including. It is possible to create a Deep Clone post-function that clones on transition. Disclaimer: I'm the product manager of this app. Try it free 👉 Deep Clone for Jira . You can set issues to default by using the "clone and bulk edit" function. Clone, bulk-clone, and customize Jira issues faster with Clone Plus for Jira! Highlights: Clone single issues or use Bulk Clone to clone many issues at once. Hi @George Toman , hi @Ismael Jimoh,. How often you need to do this and how many Epics you want to copy at a time, as well as whether or not you want to copy subtasks will determine the best solution. Click Action menu ••• > Deep Clone. The app is free for up to 10 users and you can try the app for free for 30 days. Currently it is only possible to clone single issues multiple times, as you described above. There are different ways to clone issue links (as you can see in the screenshot below). Did you know that you can bulk clone up to 100. It has seen very impressive growth of over 11% this year and is much deserved for this incredibly feature rich app. You can include comments, attachments, sub-tasks and all other issue content such as issue links. 000. Use presets to speed up cloning in Jira. Configure and create your Single CloneCloning and moving issues, templates, projects and even comments is either very difficult or not possible using standard Jira functionality. Navigate to the issue you want to clone. Jan 09, 2019 • edited. Learn more A short tutorial about Bulk Cloning multiple issue at once in Jira with Deep Clone for Jira. Due to technical constraints, not all project settings can be cloned at the moment. Automation to clone the Epic with its stories. There are several plugins that can help you accomplish this through the use of a post function. Create the new Jira project. 1. 1. 03. Free for up to 10 users ; Bulk Clone issues in Jira; Clone Jira projects; Clone epics and larger issue layers in Portfolio ; Clone and move issues to another project or issue type ; Migrate issues to another instance; Clone and edit issues Clone is the built-in default option in Jira to copy an issue. Once you've cloned the issues you must make adapt the filter of the copied board, to make sure that you display the cloned issues on the new board. There are multiple ways of cloning your issues. When you clone an issue (by going to 3 dots menu on top right) you have further options to Clone sub-tasks, Clone links and Clone sprint value. There is an option to create a project with a shared configuration that copies the settings from a project to another, but it. copy confluence pages; deep. 5 answers. Click Deep Clone. For more details you can read through our documentation, or watch our demo video. The Deep Clone button a function that you get when you install app Deep Clone for Jira . Deep Clone is a Jira add-on that can bulk clone up to 100,000 issues or entire company-managed projects, including settings, versions, components, and issues. . #1 cloning app for Jira. Free for up to 10 users ; Bulk Clone issues in Jira; Clone Jira projects; Clone epics and larger issue layers in Portfolio ; Clone and move issues to another project or issue type ; Migrate issues to another instanceYou might also consider a Marketplace app called Deep Clone which will clone the Epic and the children of the Epic. When you clone an issue, you have the ability to choose to include sub-tasks, attachments, and links. After the issue is created, you may branch to it and then use the Comment Issue action. Tendrá que agregar personas manualmente al proyecto. You can rest assured that only issues that users have access to can be cloned using Deep Clone for Jira, no. Just create a Webhook (using the first option, “Issues provided in the webhook HTTP POST body”) and adjust Deep Clone with the Webhook URL: Make sure that the Jira Automation rule is either global or, if it’s a “Project rule. I have tried using Deep Clone, and when I follow the instructions to do this I realise that the Deep Clone app only clones certain components. Jira service desk Copy links and linked issues. I select Bulk Clone -> Source Project -> Target Project. A user can change the summary while cloning it. There could be different reasons why the Deep Clone button is not available anymore. Cloning a standard project tasks list is possible with our app. I do not use any conditions on the clone, but I might change that so that the rule on triggers on "automation by Jira" rather than a user based edit. Rising Star. . changing each link in the summary image below]. Deep Clone for Jira takes all that pain away. Just check "Clone issue multiple times" under advanced options and define how often the issue should be cloned. 3 answers. Best, Marlene. Unfortunately this update doesn't work for insight fields as they are not supported by the Jira API. 2. Read more. ( Update Nov 25, 2020: It is now possible to clone entire projects with Deep Clone for Jira) 2. We've just released an update that enables you to clone projects, including tasks, project configurations, components and versions with Deep Clone for Jira. If you want to trigger a clone from post-function, you can work with the Deep Clone workflow post-function. While Jira has an option to move an issue to another project, this service isn't available to apps or integrations like Automation for Jira. 3 answers. Currently it is possible to clone the Sprint ID with our app. Our app can be integrated with Jira Automation using looping transitions. Free for up to 10 users ; Clone and move Jira issues into other projects or issue types ; Bulk Clone up to 100,000 issues ; Clone epics and entire issue trees including initiatives and other issue layers in Portfolio ; Clone Jira projects including boards, issues and moreAbout Deep Clone for Jira . 03. Navigate to a project’s settings and click on Project automation (will most likely need Administrator role in the project depending on how permissions are configured. An advantage is, that Deep Clone is pretty simple to use and you don't need any special skills to work with it. 0 votes. Our app can clone and move up to 1000 issues in one action without losing comments, subtasks or other content. Once the sub-tasks are all cloned, it clears the label. That could be done when the value of the custom field changes. Hi @Eduard Diez Kindly follow steps to remove Clone button. I would like to keep a copy of the form and attach it to the new issue. Power BI Connector for Jira. Clone and edit issues. Submit the Client ID and Client Secret of the generated Xray API key. Deep Clone can be used to clone within the same instance and between instances. Update: We released an update that enables you to clone Epics and larger issue trees multiple times. Our Marketplace app Deep Clone for Jira is also able to clone Epics along with stories and subtasks. Single Clone. swati gupta Aug 23, 2019. Click in the search box in the top navigation bar. The access to the app was restricted. But when the cloning is complete the new project does not have all of the epics with the issues (subtasks). May 10, 2022. This could be a fitting solution if you want to keep the issues in the old projects. Once the instances are connected, cloning is pretty simple and can be done by every Jira user who has access to Deep Clone. There is 1 Jira project and its related Jira Service Management project and 1 Confluence space. Deep Clone for Jira is a Cloud only advanced cloning app that lets users go far beyond Jira’s native cloning functionality. Free for up to 10 users ; Bulk Clone issues in Jira; Clone Jira projects; Clone epics and larger issue layers in Portfolio ; Clone and move issues to another project or issue type ; Migrate issues to another instanceAbout Deep Clone for Jira . Filter for all issues you want to clone. If you don't want to change the issue status to trigger a clone, you can. Thanks again for the quick response. Aug 31 2023: Support adding Epic/Tree clone presets as an action to issue menu. Filter for all issues you want to bulk clone by JQL, a favorite filter or project. To clone an issue, just select clone from the Actions menu. Some of the add-on’s most common use cases are. 7k installs. Click on the top right Actions menu ••• > Deep Clone. So the procedure of copying issues from a classic to a next-gen project using Deep Clone should be smooth and easy now. Click Project Clone in the Jira navigation on the left. Filter for the issues you want to bulk clone using the Jira issue search. 7 / 4 92. About Deep Clone for Jira . If you don't want to do this manually or if you want to clone many tasks at once, I can recommend Deep Clone for Jira, which supports your requirement. If you need a more powerful clone function our Deep Clone for Jira app can clone comments and a lot more. We are planning to use Deep Clone for Jira to provide the external organization. In Jira, navigate to Apps > Manage your apps > Deep Clone > Third-party integrations. ( Update Nov 25, 2020: It is now possible to clone entire projects with Deep Clone for. Bulk Clone a large Number of Issues. Prerequisites. Discover how Elements Copy & Sync can help your team. JRASERVER-1558 Deep copy an issue to the same project or a single project. I have created an issue type for each task in my template. You can also use our Clone and Edit feature to set your due dates dynamically with Jira expressions. It is possible to work with team-managed and company-managed projects in a Jira cloud instance. It is possible to clone checklists of Smart Checklist for Jira with Deep Clone. Solved: I have been using Deep Clone for sometime to move content from team managed project to company managed projects and have run into the issue. Learn more A short tutorial about Bulk Cloning multiple issue at once in Jira with Deep Clone for Jira. We support cloning of field/issue values that cannot be cloned with the Jira standard clone (e. Mostly this works ok but the problem I'm experiencing is the epics/issues in the cloned project still link back to the. 1) issues? Thanks& Best regards. Ultimate Guide to clone and move Jira issues. Migrate issues between instances. Cloning a Jira Project. Free for up to 10 users ; Bulk Clone issues in Jira; Clone Jira projects; Clone epics and larger issue layers in Portfolio ; Clone and move issues to another project or issue type ; Migrate issues to another instanceIf you want to bulk clone issues on Jira Cloud you can use our app Deep Clone for Jira. With our app you can clone epics and larger issue trees, including their child issues. To Deep Clone the record, you have to pass the isDeepClone parameter as true as. Click Project Clone in the Jira navigation on the left. To bulk clone all issues in one Sprint you simply have to. In JIRA I can clone an epic and its subtasks using JIRA deep clone. I'm accomplishing this through a ScriptRunner post function, 'Clones an issue and links'. Configure and execute the Deep Clone: Bulk Clone function. With our Jira cloud app Deep Clone for Jira you can bulk clone issues between two or more Jira instances. Next to the Create button, select Apps > Deep Clone. Is this possible? I've tried copying the form in the automation rules, and it doesn't seem to work. Deep Clone for Jira. So our client's solution is to clone the original issue and move the clone into the development project. Note: Deep Clone doesn't create a new sprint, when you select "sprint" in the bulk clone dialog. Navigate to the issue you want to clone. And the Jira project, in turn, became a template for further projects as the team used the Deep Clone Jira add-on to clone it when needed. Filter for the issues you want to bulk clone using the Jira issue search. SOC2 certified for enhanced security. You must be a registered user to add a comment. action: comment on issue. With this tool, you’ll have the power of bulk cloning and moving operations at your fingertips — across projects too. To export a workflow for use on your Jira Server instance: Select > Issues. You can use Clone Plus for Jira Cloud to clone an epic with its tasks and their subtasks to the same or another project. Deep Clone for Jira. Sure - Go to Settings > Issues > Workflows. Select the issues you want to clone. Select Next. * if summary starts with "Clone -". Migrating issues is possible between all Jira project types (company-managed, team-managed, software, JSM). Free for up to 10 users ; Bulk Clone issues in Jira; Clone Jira projects; Clone epics and larger issue layers in Portfolio ; Clone and move issues to another project or issue type ; Migrate issues to another instanceActivate and deactivate one of Jira features - Deep Cloning. Here is what I recommend: Field Configuration Check: Make sure that the custom fields (Product type, Short text field, Artwork Type) are present in both the source (Jira service) and target (Work Management) projects. When configuring the clone job you need to select Clone Xray Test details under Advanced options. Detailed screenshots that require configuration: Clone epic and set assignee to User who triggered the event . Thanks, Answer. For instance: Clone entire issue (subtasks, comments, worklog, everything) Clone with subtasks only; Clone with new reporter; Clone without subtasks; Clone linked issues; Etc. We are using Deep Clone for Jira Cloud as a workaround to not having project templates. You might be able to build something the the Automation feature that triggers for Issue Created and has a condition around "issue has a 'clones' link", and then change the Report field for such issues immediately after creation. It is possible to clone issues with Single, Bulk, Epic/Tree, and Post Function Clone. Change the filter to the target project or click on Edit filter Query to edit the filter to display issues of the. Deep clone is a similar functionality offered by a marketplace app called deep clone for Jira, which extends that functionality. Another reason we use Deep Clone is because it can clone. Select Clone. Configure the cloning settings: Select the target project in the production instance. Clonar reglas de automatización de jira a otro proyecto. Mar 17, 2021. If you have questions or feedback, don't hesitate to contact us directly, @prashantgera. You can integrate our app Deep Clone for Jira with Jira Automation in order to clone issues along with comments. Hi Drishti actually you can't copy from sandbox to production. I can update files during the clone step (see attached image), the only thing that. You can use Deep Clone as a tool to migrate thousands of issues to another project or instance. Watch. Attached is a screenshot of the deep clone set up, could anyone advise why the some custom fields may not be cloned. - Add Conditions, Validators, Post Functions to the Clone, Edit operations . csv to the new project, and it will auto-create the custom fields from the "Cloned" project, the renamed fields, the change drop downs, and auto-import the line items, etc. At the same time, the original ticket must remain in the Jira Service Desk project. Once the REST API is released you should be able to get data out of the form and add it to the. Our Jira cloud app Deep Clone for Jira is able to (bulk) clone and move tickets to other projects and/or issue types. Configure and create your Epic/Tree Clone. What are the best automated options to move or clone issues from one project to another while preserving the attachments. Single Clone. Is there another way to copy / clone a jira project? I see that I can potentially export the issues to a csv or other formats, but this obviously is not ideal. Use existing issues and projects as templates and customize what you copy from them so Project managers or Scrum masters can quickly fill an Epic, Sprint or Project. 2021 was an excellent year for Deep Clone for Jira as. Ask the community . If you manually edited and revoked. I am the product manager of Deep Clone for Jira. Deep Clone for Jira is not available for Jira server. Edit field values before cloning an issue. When I/we clone a request, the reporter field is not updated with a "new" reporter - the person who is cloning the request should become the reporter. To give a bit of background, I have created a template project in Jira. Yes, you can clone entire company-managed projects, including settings, Epics/Stories, etc. Here is the scenario, I have an internal company-managed board and want to create several team-managed boards for clients. Change the filter to the target project or click on Edit filter Query to edit the filter to display issues of the. Click Action menu ••• > Deep Clone. I have found add-ons that are manual, I am looking for an automated solution like jira automation. Deep Clone for Ji. Select the "Theme" which is the parent issue for all Initiatives, Epics and Stories/Tasks/Tests. board created. Our mission is to enhance your Jira and Confluence instances, remove redundant work and make your day-to-day work easier. Bulk Clone issues in Jira. However, in order to clone the full content of a project, I would strongly. Products Groups Learning . My recommendation would be to check which issues haven't been cloned and try to create one of them manually. It is is highly flexible and suitable for a variety of us cases. You can also maintain links/dependencies while cloning. Web links and confluence links are cloned as web links. Please note, these errors can depend on your browser setup. Filter for all issues you want to bulk clone by JQL, a favorite filter or project. We own the IP that they have created. Clone Epics. If this problem persists, please contact our support. Feb 9 2022: Enable data residency for Deep Clone for Jira. The issue we have found is despite using the correct copy functions not all fields are being cloned so valuable information is being missed. And the Jira project, in turn, became a template for further projects as the team used the Deep Clone Jira add-on to clone it when needed. From my research, it looks like the ability to clone/copy a jira project is only available to Jira cloud Deep Clone Feature. The problem is that I have to go in to each subtask, grab the hyperlink, and copy that into each individual instance of embedded JIRA link in the newly cloned confluence page [i. JRASERVER-6404 Bulk clone issues,. We now want to separate them into 2 dedicated projects in the same Jira instance. Search for the Workflow and click on Edit. Select the Epic you want to clone. Yes, it's possible to clone classic Jira projects along with attachments and comments with our app Deep Clone for Jira. The built-in clone feature in Jira will only clone the issue into the same project and same issue type. A short tutorial about Bulk Cloning multiple issue at once in Jira with Deep Clone for Jira. It also offers advanced cloning functionality such as bulk clones, cloning between cloud instances, and automated cloning via a post function. By default Deep Clone Global Permissions are set to public. Deep Clone for Jira now allows to bulk-clone up to 1000 issues at once within Jira Cloud. The original repository can be located on the local filesystem or on remote machine accessible supported protocols. If this problem persists, please contact our support. Aug. We also have Zephyr Scale tests to be included. 2. The Next Gen projects seem to not have the feature of copying the children issues like in the classic project, which is how you outlined. Here is the scenario, I have an internal company-managed board and want to create several team-managed boards for clients. Like • Deleted user likes this. There are two ways to access the Project Clone functionality: Option 1: Project Clone from the Deep Clone Navigation. You can also see how it works in this Epic Clone demo video. Deep Clone for Jira is the most powerful. Autocomplete in Create issue dialog. The Deep Clone button a function that you get when you install app Deep Clone for Jira . Clone Jira issues between cloud instances. I believe Deep Clone for Jira would be suitable for your use case. Select "Epic/Tree Clone" and follow the instructions on the Deep Clone dialog. Otherwise,. comments, issue status). either by adding a Deep Clone workflow post-function; or by integrating Deep Clone with Jira Automation ; In both cases attachments can be cloned. I am the product manager of Deep Clone for Jira. Clone. As a workaround, there are some Marketplace apps that might add this functionality to Jira, like the one below: Deep Clone for Jira1) Create a story and create sub tasks under this story. Deep Clone is a Jira add-on that can bulk clone up to 100,000. You can read more about that topic in our documentation: Integrate Deep Clone for Jira with Jira Automation ; Deep Clone workflow post-function ; If you have questions or feedback about our app, don't hesitate to contact us. Hence I deactivated this feature but did not uninstall the functional feature. With our App you can clone Epics and larger issue hierarchies. With this app, you can create clone operation and configure clone options, target project, issue type, copy comments, copy attachments, and more. This is not possible out of the box with JIRA. Prerequisites. Option 1: Native Jira options to clone and move issues. 1 answer. You can also create presets for standard cloning actions, to avoid cloning mistakes. With our app you can clone Epics and larger issue trees and move them to other projects while cloning. While it is possible to clone hierarchies with Jira Automation, this can be quite finicky and can break easily if project or issue configurations change. When a user triggers the "Clone Epic" recipe from Epic DEV-1, Copy & Sync will clone the Epic to any target project along with the three issues within the Epic and the. Users can bulk clone thousands of issues, issue hierarchies, or entire projects. Cloning a Jira Project. Deep Clone for Jira can be used for cloning issues from one Jira Cloud instance to another. How to Clone Xray Test Details. RULE DETAILS: Check the box "Allow Rule Trigger". So the procedure of copying issues from a classic to a next-gen project using Deep Clone should be smooth and easy now. This is sort of like SVN checkout, except the. Atlassian was able to save around 6 months of work, thanks to Deep Clone for Jira. I'm trying to clone an issue from a Service Desk project into a Jira Software project (automatically, using Jira Automation or something like it). Unfortunately, we do not support cloning Test Plans at the moment. You can trigger a Deep Clone with Jira Automation by adding a Deep Clone post function to a (looping) transition. Open the Bulk Clone dialog. Navigate to the issue you want. About Deep Clone for Jira . Mar 29, 2021. 10,701 installs. Project Clone. Jan 31, 2023. Show more Show moreDifferent Deep Clone Types Single Clone: Duplicate a single Jira issue. Since Deep Clone offers also some more advanced cloning options you might not have to update data after cloning. Original request description. . Create . ) 2. Please navigate to Jira Settings ⚙ > Apps > Deep Clone > Advanced Project Clone to get started. . Branch rule for all issues in epic. For example: trigger: whatever you are using. You can also have Deep Clone triggered via a Jira Automation if you prefer. If you don't mind using a third-party app our app Deep Clone for Jira can clone Epics with all its children. So the Deep Clone project clone is available for Jira cloud. it does not clone the status. The dialog with the cloning setup will appear → Make sure to select Clone issue properties under advanced options. 1 answerBulk clone Jira issues from search or filter results, including attachments and comments with Elements Copy & Sync. With our cloud app Deep Clone for Jira you can bulk clone Epics and all its issues in one go. Deep Clone for Jira offers a simple and intuitive tool that enables any Jira user to perform bulk cloning operations effortlessly in Jira Cloud. Supports all Jira project types, including company-managed, team-managed and Service Management projects. Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates. @mayurpandya1993 Let me know if you need help with that. Free for up to 10 users ; Bulk Clone issues in Jira; Clone Jira projects; Clone epics and larger issue layers in Portfolio ; Clone and move issues to another project or issue type ; Migrate issues to another instanceFor Jira cloud, there is now a marketplace app called Deep Clone for Jira that allows to clone Epics with all its issues, sub-tasks and sub-tasks of its issues. If you want to bulk clone and move all issues from one project to another you can try out our Marketplace app Deep Clone for Jira. You can also try to clone epics using Jira Automation:. Currently, there is no option to clone or duplicate a next-gen project. Free for up to 10 users ; Bulk Clone issues in Jira; Clone Jira projects; Clone epics and larger issue layers in Portfolio ; Clone and move issues to another project or issue type ; Migrate issues to another instanceWelcome to Atlassian Community! Forms cannot be copied between project, so at the moment your only option would be to create and attach the form as a PDF to the issue (you find this under settings for the form) and then copy the PDF over. Deep Clone is the most powerful cloning app for Jira cloud. As JIRA users we want the ability to copy / clone JIRA issues between multiple projects in such a way that all information related to the issue being copied is retained, specifically: summary, description, comments, labels, assignee and reporter, versions and components plus all the content stored in the custom fields. Clone and move issues to another project or issue type. RULE DETAILS: Check the box "Allow Rule Trigger". The chronology of tasks would be: 1. About Deep Clone for Jira . You must be a registered user to add a comment. Note that Deep Clone. Since we're mapping the fields and field values by name and not field ID, we are able to copy most issue field data between Jira projects and project types. Branch rule for all issues in Epic - clone and update summary to be something like "Clone - { {triggerIssue. Whoa. Configure and create your. It is possible to bulk clone thousands of issues between Jira cloud instances with the Deep Clone Instance Clone. As mentioned by Daniel Eads cloning between classic to next-gen projects is possible with our cloud app Deep Clone for Jira. 3. Open the Bulk Clone dialog. If you've already registered, sign in. If you don't want to change the status to trigger a clone, you can work with looping transitions. Deep Clone for Jira offers a simple and intuitive tool that enables any Jira user to perform bulk cloning operations effortlessly in Jira Cloud. Click Deep Clone. Click Deep Clone in the issue's action menu.