Luka Hummel - codefortynine Atlassian Partner

Hi @Trudy P Claspill If you're looking for a convenient way to move issues from one Jira/JSM Cloud project to another, our app Deep Clone for Jira is an excellent solution. Unlike the manual "clone & delete" approach, Deep Clone allows you to easily clone issues between projects, retaining essential content such as: *…

Hi @Armelia McCord and welcome to the community! Cloning child work items within an Epic can be efficiently managed using our app Deep Clone for Jira. Deep Clone is specifically designed for such scenarios, offering a dedicated Epic/Tree Clone feature. This functionality enables you to easily clone an entire Epic,…

Hi @Hajin Moon Jira’s built-in clone functionality has certain limitations —especially with complex workflows or cross-project setups. Our app, Deep Clone for Jira, addresses exactly this type of issue by offering robust attachment cloning capabilities. With Deep Clone, you can reliably: * Clone Attachments: All…

Hi @Norman Daryl Esponilla and welcome to the community! If you're looking to streamline your project setup by copying the board configurations (statuses, swimlanes, columns, etc.) from the original project, our app Deep Clone for Jira can significantly simplify this process. With Deep Clone, you can easily clone entire…

Hi @SianS If you want to avoid the "CLONE - " prefix in future and are willing to use a Marketplace app, our app Deep Clone for Jira can clone issues with custom prefixes or no prefix at all. Deep Clone offers a range of powerful cloning features designed to save you time and effort, especially when managing large-scale…

Hi @Lara Sousa If you're looking to automatically clone a task along with all its subtasks daily, and are willing to use a Marketplace app, our app Deep Clone for Jira provides a straightforward solution. While Jira's native automation doesn't fully support subtask cloning directly, Deep Clone integrates with Jira…

Hi @Vikrant Yadav When you create a project with a shared configuration, Jira only copies the settings – it leaves every issue/work item behind. The same is the case for the Jira Enterprise exclusive Custom Project Template feature. If you’d like those 1,000 template tasks to appear in every new project, our app Deep Clone…

Hi @Bhushan Naga [ CONT-Type1-THUNDERSOFT INDIA PRIVATE LIMITED ] When you use Jira’s built-in Clone action, all comments are technically new objects in the target issue. Jira therefore assigns each cloned comment the current date & time rather than the original timestamp—there’s no way to change that behavior in Jira…

Hi @Ahmed Saci If you want your “Clone Epic” workflow transition to duplicate the Epic and every child Story / Task exactly as you described, you can make this happen with our app Deep Clone for Jira and its integrated Epic/Tree Clone post function.

Hi @Husam Oqer and welcome to the community if you already have one project that already contains the tasks and sub-tasks you want to reuse, the fastest way to turn it into a reusable template is to clone that project with our app Deep Clone for Jira and then keep the original as your template. Whenever you need another…

Hi @Suresh Sakhare If you're frequently migrating data between projects and need a more reliable solution to avoid data loss or misalignment, our app Deep Clone for Jira might be exactly what you're looking for. Deep Clone can seamlessly clone and migrate issues, including many fields and data that aren't supported…

Hi @Eduardo If you're looking to replicate complete workflows from one Jira Cloud instance to another—including all transitions, post functions, conditions, validators, and statuses—then our app Deep Clone for Jira could help you. With its Instance Clone feature, you can clone projects across instances. This will also…

@Mark Farmer Understandable. You could try using the Jira API yourself to retrieve the original Summary value. Then you might be able to copy the text in its ADF format and edit the issue via the API.

Hi @Karl Lewis If you are willing to try a marketplace app, you can give our app Deep Clone for Jira a shot. Deep Clone can clone all issues of a project to another project.

Hi @Ayush Pathak If you are willing to use a marketplace app, you can try our app Deep Clone for Jira. Deep Clone can clone whole projects and issues, including the configuration across instances. You can read more about that here.

Hi @Mark Farmer, The Jira automation smart values will strip the more advanced features of the Atlassian Document Format from your rich text values. If you are willing to use a marketplace app, our app Deep Clone for Jira can copy the raw storage format of every field, so the new issue looks exactly like the template –…

Hi @Brian Taylor, If you are willing to use a marketplace app, our app Deep Clone for Jira removes these cloning road-blocks in one go. From a single dialog you can clone one issue or 100 000 and carry over: * Comments – with original timestamps and authors intact * Attachments, work-logs, watchers, votes and even the…

Hi @Danny Marshall what you are running into is a current limitation of Jira Automation: while it can create new issues, it cannot carry over a Jira Service Management form. If you need every newly-created ticket in your branching rule to contain an exact copy of the original form (including all field values) and are…

Hi @donna_cloutier_lawsonproducts_com and welcome to the community! Jira Cloud itself doesn’t let you copy / export a team-managed workflow on its own, but you can replicate the workflow (and the rest of the project configuration) in a few clicks with our app Deep Clone for Jira and its Advanced Project Clone feature. If…

Hi @mrmi Müller Michael and welcome to the community! Jira Automation’s built-in Clone issue action unfortunately copies only the target issue itself – it does not replicate the issue links that connect template stories to one another, so the relationships are lost in the newly created Epic. If you would like those “is…

Hello @Youmna Alomari 👋 If you are willing to use a third party app, you can skip the manual step to create a Kanban board entirely by cloning your template project with the Project Clone feature in our Deep Clone for Jira app. * Configure Deep Clone's Advanced Project Clone feature. * Open Apps > Deep Clone → choose…

Hi @Claudia Riverin 👋 Jira automation can create the follow-up issue in project #2, but today it can’t bring over Jira Service Management forms and many other details. If you want the new ticket to look exactly like the original request —including all form answers, custom-field values, comments, attachments, watchers, even…

Hi @Mayuresh T Athalekar With our Deep Clone for Jira, you can swap the default “CLONE –” prefix for the value of your Customer name field while you clone: When cloning with Deep Clone, you can disable the prefix option, so no prefix is set. Then you can use the Field Editor feature with a Jira expression like this…

Hi @Tim Lee What you are seeing is expected: Jira Automation’s built-in “Clone issue” action leaves the Request Type blank. To keep the Request Type automatically, you can use Deep Clone for Jira instead of the default clone.

Hi @Mariel Baluja Deep Clone for Jira should clone all comments. If you are encountering problems and not all comments are cloned as expected, please contact our support here.

Hi @Mariel Baluja Jira Automation doesn’t copy comments across projects without additional setup, but our app Deep Clone for Jira does it comfortably. Here's how: * Open the Epic > Actions menu ··· > Deep Clone > Epic Clone. * Pick your PMO project as the target. * Tick Comments (plus any other data you need) and create…

When you create a Software project in Jira Cloud you’ll see Atlassian’s ready‑made templates (Scrum, Kanban, Bug tracking, etc.). * Open Projects>Create project. * Select Software development. * Pick the template whose issue types and workflow suit your team. This is perfect for starting from scratch, but what if you…

Hi @Brian Donaghy If you are still struggling with cloning and are willing to use a marketplace app, our app Deep Clone for Jira you can move or copy issues to another project including the original reporter, assignee, comments, work-logs, status and many other details – even across company- and team-managed projects. *…

Hi @Ramsi Hawkins If you're open to using a marketplace app, our app Deep Clone for Jira can help streamline this process significantly. With the Bulk Clone feature, you can define a set of standardized issues in a template project and clone them across multiple projects in just a few clicks. This is ideal for release…

Hi @Bryan Grosbach 👋 If you are willing to use a marketplace app, you can have every issue in your training-setup Epic come out of the clone already assigned by letting Deep Clone for Jira do the work for you: * Run an Epic/Tree Clone Open your template Epic > ••• > Deep Clone > Epic/Tree Clone. * Set the assignees in…