Luka Hummel - codefortynine Atlassian Partner

Hi @Ward Schwillens_ Schwillie 👋🏼 In Jira Cloud, there isn’t a native “generate an Epic → Task → Sub-task hierarchy from a reusable template” feature. The easiest is probably to maintain actual issues as the template and clone them whenever needed. With our app Deep Clone for Jira, you can do this in a way that’s…

Hi @Shawn Wallace If your goal is to “copy the project”, our app Deep Clone for Jira with its Project Clone feature is usually the fastest way to get a consistent result without needing to know the original template. One important expectation for Jira Service Management: some JSM-specific configuration (like portal/request…

Hi @Han Dee and welcome to the community! Yes, it is possible to copy (most of) a project’s configuration without copying the existing issue data - both with native Jira features and, more flexibly, with our app Deep Clone for Jira. There are two slightly different scenarios: * Same Jira site (same base URL as the other…

Hi Jennifer, Your use case – a sequence of JSM tasks where each new task should show all comments from the previous ones – is a good example of where our app Deep Clone for Jira can simplify things compared to building complex Jira Automation rules. Deep Clone provides an easy way to trigger the cloning of your issues with…

Hi @Elyse Algate As Hermance already described, there’s the built-in move feature, but I’d like to add some context from the “cloning/migration” side to your question and where our app Deep Clone for Jira can help. If you ever need to go a bit further than what the built-in move gives you; for example: * Consolidate JPD…

Hi @Timothy McKay Using CSV templates can be quite error-prone, especially if you change project configurations or want to use the template in different projects. If you are willing to try a Marketplace app, our app Deep Clone for Jira can help you to reproduce your templates as often as you want and will help you to get…

Hi @Asier Vadillo By default, Jira’s built-in clone function will copy most fields, including custom fields, but does not provide a way to exclude specific fields from being cloned. There is no native setting in Jira Cloud to define which custom fields should or should not be cloned. If you need more granular control over…

Hi @Taras Boianovskyi If you are willing to use a Marketplace app, our app Deep Clone for Jira can help you to duplicate your ticket for escalation and keeping the attachments. Two practical ways to set this up * On-demand from the issue view (fastest to try) * Open the request ticket and click Actions (⋯) → Deep Clone. *…

Hi @guillaume.baron If you are willing to use a Marketplace App, you can try our app Deep Clone for Jira. With its Instance Clone feature, you can freely clone projects (spaces) and/or work items between production and sandbox environment. You can also use the Field Editor feature to redact data by clearing or editing…

Hi @Nagasaka Goro and welcome to the community! If you want to copy data from one Jira Cloud environment to another without CSV export/import, you can use our app Deep Clone for Jira and its Instance clone feature. It lets you move entire projects or just selected issues between Jira Cloud instances. While Deep Clone…

Hi @Pavan Kumar Deep Clone for Jira is Cloud Fortified and you can find more information regarding our security on trust.codefortynine.com.

Hi @Matt Baker if you are willing to use an Atlassian Marketplace app, you can absolutely clone a JSM issue from between instances and include attachments automatically. That’s exactly what our app's Deep Clone for Jira Instance Clone feature is for. How to set it up once * Have an admin in both instances go to Apps >…

Hi @Witt, Laura Kristin (MRB-R) and welcome to the community! If you are willing to use an Atlassian Marketplace app, our app Deep Clone for Jira can help you with your questions: * Put newly created/cloned issues straight into the current sprint * Deep Clone dialog → Sprint: When cloning, tick Sprint to carry over the…

Hi @Yogesh Mude In Jira Cloud, automation rules unfortunately can’t transfer attachments between two different sites. That’s why your rule is able to create the issue in the target instance, but not move attachments over. If copying attachments is a key part of your workflow, and you are willing to use a marketplace app,…

Hi @Omkar Rajale If you are willing to use a marketplace app, you can implement your “template → derived projects (A/B) with optional tweaks” setup in Jira Cloud with a mix of Jira’s shared schemes and our app Deep Clone for Jira’s project/issue cloning. Here’s a practical way to do it: * Create a company-managed…

Hi @Vidya Subramanya, If you want a Jira Cloud dashboard that shows overall project performance and helps you spot schedule risks, you can build it with our app Quick Filters for Jira Dashboards. If you’d like, you can try our demo dashboards (no install needed) or install a trial from the Marketplace.

Hi @Elia Kouruklis and welcome to the community! You won’t get a blinking menu badge in Jira dashboards, but you can build a clear “traffic-light” style alert directly on the dashboard with our app Quick Filters for Jira Dashboards. * Add the Quick Controller gadget and set a filter for Status = Backlog (or use a JQL like…

Hi @RomainCUVELLIER and welcome to the community! From what you describe, you need to clone Jira issues from your template (tasks + subtasks), ideally within the same project and in bulk. That’s exactly what our app Deep Clone for Jira is built for. Two quick ways to spin up a fresh copy of your template work * Clone a…

Hi @Kasja Maksymiak and welcome to the community! You’re right to suspect that Jira Cloud doesn’t provide a native, self-service way for other teams to copy a parent issue together with all its child work items into their own projects in one go. You can approximate it with automations, but that still needs setup and…

Hi @Sudarsana G If you are willing to try a marketplace app to clone your issues, our app Deep Clone for Jira could help you. With Deep Clone, you can clear fields of the cloned issues: * Open Deep Clone via More (•••) → Deep Clone. * In the dialog, enable Edit fields and click Open Field Editor ✏️. * Add your custom…

Hi @Ryan Läemmle and welcome to the community. If you are already using Deep Clone for Jira to clone your templates, you can use the Field Editor with Jira Expressions to calculate the new Start and End Dates based on other custom fields present in your template (like your 'estimates') while cloning the template issues.…

Hi @bauer and welcome to the community! While Jira Cloud itself doesn’t offer native support for full project templating, you can achieve exactly this with the help of marketplace apps. Our app Deep Clone for Jira lets you: * Clone entire projects, including issues, components, versions, and (with Advanced Project Clone)…

Hi @orla_mears Jira automatically adds a "clones" issue link between the original and cloned issues when using the standard Clone function. If you'd like to prevent this link from being created when cloning issues, our app Deep Clone for Jira offers a flexible solution. With Deep Clone, you can simply uncheck the option…

Hi @Denilson Cardoso and welcome to the community! If you’re looking for a reliable way to clone issues across projects - including custom dropdown fields and other advanced issue content - I’d recommend trying out our app Deep Clone for Jira. Deep Clone for Jira supports: * Cloning custom fields like single- and…

Hi @karine_aittaouit, If you want to automatically create an Epic together with all its child issues based on a predefined structure, our app Deep Clone for Jira offers a flexible and powerful solution. With the Epic/Tree Clone feature, you can: * Clone an Epic along with its entire hierarchy of child issues (e.g.,…

Hi @Naresh Rajak Since Jira's built-in functionality doesn't allow you to clone a project with its configurations (fields, workflows) without bringing along issues, I recommend using our app Deep Clone for Jira. With Deep Clone, you can effortlessly clone Jira projects without issues, while retaining important…

Hi @Charlie Niu and welcome to the community! If you are willing to use a Marketplace app, our app Deep Clone for Jira can help you with that. Deep Clone can Bulk Clone up to 100,000 issues at once and has an integration with Xray which allows the cloning of Xray Tests.

Hi @igregg and welcome to the community! With our app Deep Clone for Jira, you can automate cloning your issues with all its child issues. You can use a Jira Automation to trigger an Epic/Tree Clone post function and clone them according to your schedule. You can read more on that in our documentation.

Hi @Josh Thaler and welcome to the community! It looks like your CSV import is updating because you’re including an Issue Key column (or another unique identifier) in your template. Jira’s CSV importer will always match on a key if one is provided, and update that existing issue rather than creating a new one. I’m with…

Hi @Trudy P Claspill I think you have understood it perfectly. There are some custom fields Deep Clone can't clone. We have collected them in our documentation.