1. Deep Clone is available for users of Jira Cloud. It is possible to bulk clone thousands of issues between Jira cloud instances with the Deep Clone Instance Clone. Both clone and move are available from the Actions menu. This is extremely time consuming. Clone Epics. Clone Epics. go to all Boards view and select create board. Ask a question Get answers to your question from experts in the community. 7. Like • Marlene Kegel -. Luego, puede tener algunas reglas de Automation For Jira que se ejecutan para crear el conjunto inicial deseado de problemas en el proyecto. This is how you can set up a Jira Automation with (global) looping transitions. Advanced cloning of single issues, a bulk of issues or projects. It’s possible to clone certain data that is usually not clonable (e. If you are willing to use a third-party app, our Deep Clone for Jira can help you clone whole issues hierarchies (Initiatives ⇒ Epics ⇒ Tasks/Stories ⇒ Subtasks) with our Epic/Tree Clone feature. While you can automate this, the set-up is quite tedious and the automation rule can break quickly if there are any changes. No-code Power BI Jira integration. That client board if for them to create tickets and see how are they moving in the kanban board. Configure and create your. Therefore we released an app Deep Clone for Jira that offers advanced cloning options. Once the connection is set up, a new option is available in the Deep Clone form. At best, Jira makes simple tasks like cloning and moving issues, templates, projects and even comments very difficult. My idea is to clone the original project and then filter out and bulk delete the tickets made by one or the other team. Clone Jira issues between cloud instances. You can then change the details of the cloned story. The app was uninstalled from your Jira instance. 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. You must be a registered user to add a comment. The app is free for up to 10 users and otherwise, you can try it for 30 days. Due to technical constraints, not all project settings can be cloned at the moment. My cloned stories are getting linked to the Original Epic itself with the automation I have written. It is is highly flexible and suitable for a variety of us cases. Click on the transition where you would like to do the Deep Clone. Select "Epic/Tree Clone" and follow the instructions on the Deep Clone dialog. Keep in mind, the prefix Clone is automatically added to. . You can also try to clone epics using Jira Automation:. Add a global looping transition to your workflow. Answer accepted. May 10, 2022. Workaround. Voilà! Deep Clone ensures that the newly cloned tasks are correctly linked to the newly cloned feature. Edit the Summary. Hello, In the OOB Jira you could use the following JQL query: issue in linkedIssues (ABC-123,"clone") This query would show you all cloned issues for ABC_123 issue. You can add a Deep Clone post-function to your Jira workflows and trigger clones automatically. 0 votes. However, if someone is urgently looking for a solution, I would like to refer to our Jira cloud app Deep Clone for Jira. Share. If you are not sure if the migration will work, just give it a try. The original repository can be located on the local filesystem or on remote machine accessible supported protocols. Select Epic/Tree Clone. Select Clone. Jan 13 2022: Show detailed progress while cloning a project. Cloning a standard project tasks list is possible with our app. About Deep Clone for Jira . You can include comments, attachments, sub-tasks and all other issue content such as issue links. Option 1: Native Jira options to clone and move issues. Below, the picture my automation : For now : - Epic cloning works - Stories cloning works - Tasks cloning doesn't work - Sub-tasks cloning works but all cloned Stories or Tasks sub-tasks are move in the Epic and not on their real parent issue. About Deep Clone for Jira . . 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. It is possible to clone issues with Single, Bulk, Epic/Tree, and Post Function Clone. The JIRA Command Line Interface and using its cloneProject command. You are flexible to decide which field you want to clone, and which not. About Deep Clone for Jira . In Jira, navigate to Apps > Manage your apps > Deep Clone > Third-party integrations. If you've already registered, sign in. About Deep Clone for Jira . More details. Clone Jira projects. Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates. Option 2: Project Clone from the Bulk Clone dialog . For instance: Clone entire issue (subtasks, comments, worklog, everything) Clone with subtasks only; Clone with new reporter; Clone without subtasks; Clone linked issues; Etc. You can access the project clone over the bulk clone dialog. Deep Clone for Jira. About Deep Clone for Jira . Clone. The best workaround is to clone the issue and delete the original: Add a 'Clone issue' action and select the project you want to move the issue to. Besides that we offer a lot more advanced cloning features, like: Clone and Move to other projects. Please note: Due to technical reasons this is only available for classic projects. It is possible to Bulk Clone up to 100,000 issues at once with Deep Clone for Jira. Automation to clone the Epic with its stories. I'll just share that I also wrote a tutorial for how to do it with Elements Copy. Now you can trigger a Deep Clone via Jira Automation without changing the status of an issue. Deep Clone for Jira is a Cloud only advanced cloning app that lets users go far beyond Jira’s native cloning functionality. My post is now updated and correct. 2021 was an excellent year for Deep Clone for Jira as it grew by 78% over the year and Deep Clone has continued its strong performance this year, growing by 7% over January. Deep Clone for Jira is the number 1 cloning app for Jira. Clone & move issues. In your Jira instance, go to Any project > Project board > View all. Don't hesitate to get in touch with our support if you have questions or feedback. At this juncture, “Deep Clone for Jira” emerged, offering an effective solution to address the timing and technical challenges. JRASERVER-1558 Deep copy an issue to the same project or a single project. Click on Post functions. StepsizeAnd I add my ideas/line items. When cloning Jira Issues - your checklist data would be cloned along with the custom field 🎉. The Deep Clone add-on might be able to help you with that. Otherwise. Deep Clone for Jira is a Cloud only advanced cloning app that lets users go far beyond Jira’s native cloning functionality. Comment; Kate Jun 29, 2020 • edited. A deep clone is a clone that copies the source table data to the clone target in addition to the metadata of the existing table. But since Deep Clone creates clones, the original issues remain unchanged in the. Configure and execute the Deep Clone: Bulk Clone function. cancel. Select the target project and configure you clone. Note: Deep Clone doesn't create a new sprint, when you select "sprint" in the bulk clone dialog. Filter for all issues you want to clone. Create the new Jira project. About Deep Clone for Jira. Jira Cloud Pricing: Free for up to 10 users; If more than 10 users, $0. With our Jira cloud app Deep Clone for Jira you can bulk clone issues between two or more Jira instances. Clone an issue to another project based on a custom field during a workflow transition. @mayurpandya1993 Let me know if you need help with that. @kriegaex Deep Clone offers advanced features that either don't exist in Jira or require complex configuration. Automate cloning by adding a Deep Clone post function to your workflow. In Deep Clone you can e. . Deep Clone can clone all comments of your issues in one go. Unfortunately this update doesn't work for insight fields as they are not supported by the Jira API. 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. let me know if this works for you. This means if the last issue that was created in the target project had the issue key ISSUE-300 , the issue key. Rule 2: Cloning those newly-created Tasks/Stories's subtasks, based on the temporary label that was added. Each has it's own release cycle, which is why they are individual projects in Jira. View More Comments. What makes this add-on truly convenient is the feature of bulk cloning that lets users manipulate up to 5000 issues at once. As the others already have said the native Jira clone function doesn't clone comments and other values. 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. At the same time, the original ticket must remain in the Jira Service Desk project. Cloning a standard project tasks list is possible with our app. So, you can update the filter to allow to see those Epic and task. Post Function Clone. 7. You can integrate our app Deep Clone for Jira with Jira Automation in order to clone issues along with comments. In the post functions tab, select “Deep Clone”. Currently it is possible to clone the Sprint ID with our app. Deep Clone for Jira offers a simple and intuitive tool that enables any Jira user to perform bulk cloning operations effortlessly in Jira Cloud. The clone gets triggered by a post-function, but since the transition is looping the status won't change. The clone can be moved to another project and issue type while cloning. When clones are unsuccessful, most of the time it's because a required field or issue type isn't available, when Jira tries to create the clone. If cloning a very large number of issues at once cannot be avoided, please consider the following:There are multiple ways of cloning your issues. However, it is possible to let Deep Clone trigger a Jira. 2021 was an excellent year for Deep Clone for Jira as. Click Create rule. Our app Deep Clone for Jira is part of the Cloud Fortified apps program and provides advanced security, reliability, and. Or it could be done when the issue in that project transitions to Y (assuming. Deep Clone is free for instances with up to 10 users. If you are open to use a third-party app, our Deep Clone for Jira can clone whole issue hierarchies, including Initiatives, Epics, Tasks/Stories, and Subtasks. Turn on suggestions. 3. We use the add-on called Deep Clone, which will all you to change the output project and pretty much all other fields, while also allowing to you decide if you want to clone over comments, links and attachments. If your Jira/Confluence instance is in a different location than our app, you can relocate the app to your instance location. Create presets to speed up standard cloning actions. Navigate to the action menu of the "Theme". 2. If you don't set up the variables correctly, you can end up setting the wrong parent issues, or epic. In JIRA I can clone an epic and its subtasks using JIRA deep clone. Thus, check that the user has correct issue permissions. There are two ways to access the Project Clone functionality: Option 1: Project Clone from the Deep Clone Navigation. Create a NEW board in the NEW project. I've just seen your community post. 000 issues at once. Just select "Clone project. Go the Issue you want to clone → 3-dots menu → Deep Clone. Deep Clone offers advanced features, that are not available in the standard clone feature of Jira. You must be a registered user to add a comment. A short tutorial about Bulk Cloning via the advanced issue search with our cloud app Deep Clone for Jira. 3 answers. The Deep Clone button a function that you get when you install app Deep Clone 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 instance; Clone and edit issuesAbout Deep Clone for Jira . In the post functions tab, select “Deep Clone”. It's possible to clone entire company-managed projects along with settings, components, versions and issues. About codefortynine. Navigate to Filters > View all issues in your Jira Cloud instance. There are different ways to clone issue links (as you can see in the screenshot below). 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. Bulk Clone all template tasks from the template project to the NEW project. A simple solution is to clone the task first, then move it to a different project and assign the epic. Hi @Erika Yamamoto. Update: It's now also possible to clone entire company-managed projects, including issues, components and versions. So what will happen here is that as each task is cloned, it applies a unique label on the template task which will trigger a second rule to clone all of its sub-tasks. As you can select only one type of link in Create issue dialog, we decided not to show linked. Navigate to the issue you want to Single Clone. If you clone on a regular basis, you can create presets for recurring cloning actions. Hi @Florian Royer. Bulk Clone or copy project templates. The follow these steps: Select your onboarding filter as the “source filter”. 10. Admin > billing > billing details where you should be able to edit the CC details. 2021: It is now possible to create new sprints with the. . You can also see how it works in this Epic Clone demo video. The default clone option of Jira allows you to choose if you want to include attachments or not, as you can see in the screenshot below:. Click on the top right Actions menu ••• > Deep Clone. 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 instanceSome Jira email notifications cannot be suppressed by Deep Clone. . Once an issue was cloned then anytime a change was made, other than to the Version or Component, it could be applied to zero or more of the linked (of type. REST API. The git clone command copies an existing Git repository. Open the Bulk Clone dialog. We have some automation setup that will also allow you to clone issues into other projects and issue types, so we primarily use Deep Clone for those functions in manual cases. Click Project Clone in the Jira navigation on the left. Deep Clone is cloud fortified, SOC2 Type II compliant, and. For instance: Clone entire issue (subtasks, comments, worklog, everything) Clone with subtasks only; Clone with new reporter; Clone without subtasks; Clone linked issues; Etc. And the cloned issues should be in the target project. To do that, you just need to configure the Advanced Project Clone feature for Deep Clone before cloning your project. Next to the Create button, select Apps > Deep Clone. Cloning the project configuration can be done with a native Jira feature, the shared project configuration. With our Epic/Tree Clone feature, you can clone whole issue hierarchies (Initiatives → Epics → Tasks/Stories → Subtasks). With Deep Clone you can clone entire Jira projects, along with issues, project settings, components and versions. Change the target project and issue type when cloning. They can move clones between projects or cloud instances. Clone & move issues. With our app Deep Clone for Jira you can clone and move issues with attachments. Please note that the Xray “Test” target issue type has to be selected. About Deep Clone for Jira . You could use a CSV import to import the issue information, each time you need to replicate it. Click Bulk Clone in the Jira navigation on the left. 7k installs. If you need a template based approach that is simple to use, I would suggest creating a Jira Work Management (Jira Core or. Xray tests) including issue values. I get the error: "We only show target projects for which you have the "Create issue" permission, and that are not excluded by “Restrict Access” in the Deep Clone settings. 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. 4 - In the "Hierarchy" section, select "Copy full hierarchy". You can also automate cloning of issues including attachments with our Jira cloud app Deep Clone for Jira. * if summary starts with "Clone -". Don't hesitate to get in touch. Submit the Client ID and Client Secret of the generated Xray API key. I assume that your problem cannot be related to our app, because you added the tag "server" to this community post. We have consulted on your case between our teams and although Deep Clone can edit the values of most issue fields with the Deep Clone Field Editor, it is not possible to change the status of a Smart Checklist item while cloning, unfortunately. Jira Software Authentication and User Management Operational Jira. Open the details page of the app. Another reason we use Deep Clone is because it can clone. Connect Jira to Power BI and build custom Jira reports. However, in order to clone the full content of a project, I would strongly advice using an add-on such as our app, Elements Copy & Sync, to make your life easier. Is this possible? I've tried copying the form in the automation rules, and it doesn't seem to work. Filter for all issues you want to bulk clone by JQL, a favorite filter or project. # Set up the Jira API client. Francisco Cifuentes Mar 10, 2022. 2) If you already have few stories created, you have created 5 sub. Sep 07 2023: Project Clone can now be accessed directly from the Deep Clone navigation. But when the cloning is complete the new project does not have all of the epics with the issues (subtasks). So the original issues should be in the original project. When the epic is cloned, the backlog is also cloned, with the same issues, and in the same order. There is 1 Jira project and its related Jira Service Management project and 1 Confluence space. You can find the documentation on this here. The Clone Epic Template for Jira feature enables users to clone an Epic and its associated stories, sub-tasks, and checklists, which cannot be deep-cloned natively in Jira. from jira import JIRA. We support cloning of field/issue values that cannot be cloned with the Jira standard clone (e. Jeremy D Aug 17, 2021. 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 . Like Deep Clone, Clone Plus for Jira enhances Jira’s native cloning functionality and gives users more control over the issue cloning process. 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 instanceCreate an API key in Xray following these instructions. The app is free for up to 10 users and you can try the app for free for 30 days. If the Bulk Clone button is not visible, expand the menu by clicking the expand arrow. If you are a Jira administrator you can also temporarily disable outgoing mails under ⚙️ Settings > System > Outgoing Mail. Our mission is to enhance your Jira and Confluence instances, remove redundant work and make your day-to-day work easier. Copy and assign all. Change the filter to the target project or click on Edit filter Query to edit the filter to display issues of the. . The user triggering the clone shall have access to the target instance and the appropriate permissions to create issues With our Jira cloud app Deep Clone for Jira, it's possible to clone most checklists. While doing this, adding a temporary label to those newly-created Tasks/Stories. Hi @ [deleted] , You can clone an issue to a different project with the help of Clone plus for Jira app. Cloning a Jira Project. 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. 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. Deep Clone for Jira #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. I would like to keep a copy of the form and attach it to the new issue. On Jira Cloud you can use our app Deep Clone for Jira to solve your problem. Supports all Jira project types, including company-managed, team-managed and Service Management pro. Select the new project you have created with the Deep Clone Project Clone or manually. Then all of those separate requests can be managed in a bigger production board. A few days ago we released an update that fixed some issues with next-gen. Migrate issues between instances. . 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. I just mixed up "team-managed" and "company-managed" projects. To clone an issue: Open an issue. With this tool at their disposal, Jira administrators no longer need to handle such tasks exclusively, freeing up their valuable time for more critical responsibilities. When clone the issue and the sub-tasks statuses are reset to-do. With this app, you can create clone operation and configure clone options, target project, issue type, copy comments, copy attachments, and more. Currently it is only possible to clone single issues multiple times, as you described above. Reply. Clonar reglas de automatización de jira a otro proyecto. Click Try it free. Instance Clone. Clone the issue status, comments, forms, work logs, votes, watchers, Xray tests, attachments, issue links, and more. Bulk Cloning with Deep Clone is pretty easy and can be done by any Jira user. Click Project Clone in the Jira navigation on the left. Instance Clone. This functionality exists in the present version of JIRA (3. Using Deep Clone will also circumvent any potential issues regarding your automation execution limits. You can trigger a Deep Clone with Jira Automation by adding a Deep Clone post function to a (looping) transition. )In your attached screenshot I can see that our Marketplace app Deep Clone for Jira is installed on your instance. 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. Unfortunately, we do not support cloning Test Plans at the moment. But not out of the box Jira. A short tutorial about cloning an Epic (or an Initiative) with our cloud app Deep Clone for Jira. 3. Cloning the project configuration can be done with a native Jira feature, the shared project configuration. Another option to Bulk Clone epics along with tasks and their subtasks would be our Jira cloud app Deep Clone for Jira. Create the new Jira project. Select the "Theme" which is the parent issue for all Initiatives, Epics and Stories/Tasks/Tests. Hola, Estoy usando la aplicación Deep Clone For Jira. Having an issue with cloning automation. Supports all Jira project types, including company-managed, team-managed and Service Management projects. Please follow the. Users can bulk clone thousands of issues, issue hierarchies, or entire projects. Hi, Someone requested to install Deep Clone in our Jira, and in the app request page I can see that "Cost" said "Paid" but the only option Jira is giving me to install it is "Try For Free". With Deep Clone for Jira they are able to accelerate this process considerably. Under Apps > Manage your apps you can check if Deep Clone is still installed. Rising Star. The app is free for up to 10 users and otherwise, you can try it for 30 days. Cloning attachments is also possible of course. clone entire Jira projects along with all issues. You can also let Deep Clone trigger a Jira Automation Incoming Webhook on the issues created by Deep Clone. Follow this procedure. Show more Show moreDifferent Deep Clone Types Single Clone: Duplicate a single Jira issue. 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. You can use Deep Clone as a tool to migrate thousands of issues to another project or instance. Some example apps are below. Choose “same as original” as the target project. Deep Clone offers advanced features, that are not available in the standard clone feature of Jira. Deep Clone for Jira add-on is an advanced solution for cloning single issues, a bulk of issues, epics, or template projects in Jira. Your best bet is to use a Marketplace App like Configuration Manager for Jira. If the issue which is linked is also part of the bulk clone, you can create an issue link between the. 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. Our projects are Software, Company Managed. Copy the URL. Update Nov 26, 2020You should be able to clone links. With this tool, you’ll have the power of bulk cloning and moving operations at your fingertips — across projects too. Configure and create your Bulk Clone. Deep Clone is the most powerful cloning app for Jira cloud. If you are willing to use a third-party app, our Deep Clone for Jira can help you clone whole issues hierarchies (Initiatives ⇒ Epics ⇒ Tasks/Stories ⇒ Subtasks) with our Epic/Tree Clone feature. If you want to clone in bulk, then you need an app. The process is pretty simple and can be done by any Jira user. My company refuse to use Apps like Deep Clone. Discover how Elements Copy & Sync can help your team. Thank you for reaching out to. The issue we have found is despite using the correct copy functions not all fields are being cloned so valuable information is being missed. With Deep Clone for Jira it is possible to clone entire company-managed Jira projects, including settings, issues, components and versions. Check out the following ones: Indeed you can copy an entire project using our bulk clone feature, just create e new project and copy all issues at once. If you need more flexibility when cloning links, you can try our Jira cloud app Deep Clone for Jira. Cloning a Jira Project. Clone. Your link is not an Atlassian documentation link, but from the documentation of our Marketplace app Deep Clone for Jira. Clone & move issues. comments, issue status). SOC2 certified for enhanced security. either by adding a Deep Clone workflow post-function; or by integrating Deep Clone with Jira Automation ; In both cases attachments can be cloned. Filter for all issues you want to bulk clone by JQL, a favorite filter or project. If you are willing to use a third-party app, you could try our Deep Clone for Jira. Hi @Nilesh Pal and welcome to the community!. Import the . A special case of Bulk Cloning is to clone an Epic, Initiative, or other custom hierarchy levels above Epics. You can use smart values to reference issue fields to personalize the message along with setting the visibility of the comment. 2021 was an excellent year for Deep Clone for Jira as it grew by 78% over the year and Deep Clone has continued its strong performance this year, growing by 7% over January. When Deep Clone for Jira clones between team-managed and company-managed projects, it tries to match values like issue type and custom fields by their. Bulk Clone Professional offers you capability to Clone, Move & Alter field values on multiple issues in one operation. Sama Mohamed Aug 11, 2022 • edited. Deep Clone for Jira is a Cloud only advanced cloning app that lets users go far beyond Jira’s native cloning functionality. Unfortunately, there are still some known limitations when cloning Jira Service Management projects with Deep Clone for Jira. Hi @Eduard Diez Kindly follow steps to remove Clone button. Tendrá que agregar personas manualmente al proyecto. Open the action menu in the issue you want to clone. You must be a registered user to add a comment. I have created an issue type for each task in my template. Bulk Clone issues in Jira. Whether you want to clone single issues, a bulk of issues, company- or team-managed projects, issue hierarchies, clone between instances, clone, or edit specific fields or automate cloning – we provide a solution. Deep Clone for Jira now allows to bulk-clone up to 1000 issues at once within Jira Cloud. Configure and create your Epic/Tree Clone. Have you tried to clone the Epic via the "Deep Clone" button? You can read more about cloning Epics (or larger issue trees) with Deep Clone for Jira in our documentation. Bulk Clone or copy project templates. 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. Set any necessary parameters. Click Workflows. Both instances need to have Deep Clone for Jira installed. Deep Clone is a fantastic way to save time copy-pasting issue details or saving templates. All issues from linked templates will be generated right after creating an issue. There could be different reasons why the Deep Clone button is not available anymore. it does not clone the status. Bulk Clone a large Number of Issues. choose either Kanban or scrum. Select Epic/Tree Clone. You must be a registered user to add a comment. You can clone Labels, Assignees, custom fields and Components (It's necessary that the Component is created also in the target project to be cloned. I have an educational product, and my learning path takes place in Jira with many students completing it; and thanks to Deep Clone, I can clone entire projects, saving me hours every day. Jira automatically adds “CLONE” to the beginning of the summary of the. It is possible to create a Deep Clone post-function that clones on transition.