Luka Hummel - codefortynine Atlassian Partner

Hi @Mayur Gaikwad/Tech PMO, If you are looking to manage cloning issues in Jira, while Jira does not have a built-in feature to directly prohibit cloning through permission schemes, you can explore alternatives. For instance, using our app Deep Clone for Jira can help control cloning by offering advanced cloning…

Hi @Kyle Whitton and welcome to the community! It is indeed possible to trigger automation rules in the secondary project when a cloned issue is created. However, since the issue is cloned rather than created in the traditional sense, you'll need to adjust your automation rule to recognize this. One way to achieve this is…

Hi @Derick and welcome to the community! If you want a more streamlined way to clone epics along with all their subtasks and associated data, you might want to explore our app Deep Clone for Jira. Deep Clone allows you to clone entire epics with their subtasks, including custom fields, attachments, and comments, making it…

Hi @Shweta Kalra and welcome to the community! To move subtasks between projects in Jira while ensuring that comments are also transferred, you might find the default options limiting. One effective solution is to use our app Deep Clone for Jira. Deep Clone allows you to clone issues, including subtasks, along with all…

Hi @Diego Abner, I understand your frustration with setting up your Marketing Projects in Jira. One tool that could simplify this process for you is our app Deep Clone for Jira. This app allows you to clone entire projects, including Epics, Stories, Tasks, and Subtasks, preserving all the necessary hierarchy and details.…

Hi @Lianne Geerlings, To simplify copying your template and overcome issues like incompatible components, you might find our app Deep Clone for Jira helpful. It allows you to clone whole projects, issues, including subtasks and their hierarchy. You can read more how to use Deep Clone to clone your template projects here.

Hi @Steindl, Calman If you are willing to use a third-party app, you could try our app Deep Clone for Jira to replace your CSV templating process. With Deep Clone for Jira, you can clone a template project including settings and issues, even to other Jira instances. You can find more details on how to use Deep Clone for…

Hi @Igor Titov If you are having trouble creating new issues in another project while copying custom field values, you could also try our app Deep Clone for Jira. You can also integrate Deep Clone in your existing Jira Automation. Read more on this here.

Hi @Marcelo Canaparro It's great that you've set up a company-based project with custom automations and configurations. To reuse this setup for other projects, you can use the 'Share settings with an existing project' option during project creation. This will copy all the scheme settings. For automation rules, you can…

Hi @Snehal Singh That decision depends largely on how much data you want to reuse. If you have lots of custom fields that are filled and should stay filled in the new issue, cloning is definitely preferable. With only 2–3 fields being redundant, it might be better to create a new issue and copy the needed values via an…

Hi @Snehal Singh For efficiently cloning issues in Jira, you could try our app Deep Clone for Jira. This tool allows you to clone issues, epics, and even complete projects while maintaining all field values, attachments, and comments. It simplifies the process by letting you select exactly what you need to clone, making it…

Hi @RedBottle and welcome to the community. Considering your needs, using Jira projects per project/service can help maintain clarity and prevent clutter, especially when different status types are involved. You could use labels or other custom fields to link the issues to a customer. Jira projects per customer could also…

Hi @Thayne Munson I'm Luka from codefortynine the developer of Deep Clone for Jira. This error could be caused by multiple things. Could you open a ticket with our support here so we can take a look and find the underlying cause? We can also share our findings here afterward for the benefit of the community.

Hi @Rebecca Pittman and welcome to the community! It looks like you're encountering issues with your automation setup in Jira. To ensure the cloned ticket retains the correct format and information, you could try our Deep Clone for Jira app. Deep Clone offers extensive cloning capabilities, including preserving field…

Hi @Hartwig B and welcome to the community! You could try our app Deep Clone for Jira for your templating needs. You can just add specific labels to your template issues and then use the Bulk Clone feature and use the labels to either include or exclude the issues based on the labels present.

Hi @Mayuri Murugesu and a belated welcome to the community! If you are willing to use a third-part app, you could try our Deep Clone for Jira. With Deep Clone you can Bulk Clone your issues and use the Field Editor to select the Epic you want as a parent for the cloned issues for the Parent field.

Hi @Mateja Leskovec That's not a problem, you can use Deep Clone together with Jira Automations and use a normal Jira Automation trigger to start a Deep Clone. You can read more on that here. You then can also use the Field Editor feature, which allows you to set a new Parent for the cloned issue(s). Furthermore, you even…

Hi @Mateja Leskovec If you are willing to try a third-party app, you can try our Deep Clone for Jira. Deep Clone can keep the original Parent Link when cloning issues to other projects.

Hi @Jessel Bentley If you want to have the comments in your cloned comments have been made by the original posters, you can try our app Deep Clone for Jira. Deep Clone can impersonate the original posters when creating the comments in the cloned issue.

Hi @Nonla KONE and welcome to the community! Copying comments from the original issue to the cloned issue can indeed be a bit tricky. If the documentation you found didn't work due to configuration changes, and you are willing to try a third-party app, I recommend trying out our Deep Clone for Jira. This app allows you to…

Hi @Jacob Rajesh and welcome to the community! If you are willing to try a third-party app, you can try our Deep Clone for Jira. Deep Clone can trigger a Jira Automation Incoming Webhook on the issues created by Deep Clone. Just create a Webhook (using the first option, “Issues provided in the webhook HTTP POST body”) and…

Hi @Sushmita Chakraborty Make sure you have checked Clone the issue status under More options and selected either Link to cloned parent, else keep original or Keep link to original parent, depending on your use case.

Hi @Natalia Matsyuk, It sounds like you are experiencing an issue with the cloning process where the cloned issue is not reflecting the most recent changes made to its parent. If you are willing to try a third-party app, like to recommend trying our Deep Clone for Jira. This app allows for more advanced cloning…

Hi @Martina Guth, When cloning an Epic in Jira, certain relationships or links to parent or related tickets can indeed get lost, depending on the cloning method being used. This behavior is typically not considered a bug but rather a limitation of the default cloning functionality in Jira. To address this issue, you could…

Hi @Sushmita Chakraborty If you are having trouble with the standard Jira 'Move' feature and are willing to try a third-party app, you could try our Deep Clone for Jira. Deep Clone can clone your issues from your team-managed to your company-managed project and will match all custom fields as long as their names are…

Hi @Berkan Suna and welcome to the community! In Jira, the default cloning functionality does not provide a straightforward way to restrict users from cloning issues with links while allowing them to clone issues without links. However, you can achieve this by our marketplace app Deep Clone for Jira. Deep Clone offers…

Hi @Emmanuel Katto and welcome to the community! If you are willing to use a third-party app, you could try our Deep Clone for Jira. Deep Clone allows you to clone issues in bulk and move them between projects. It is particularly useful when you need to duplicate the issues in a next-gen project and transfer them…

Hi @Anth.Burnikell If you are willing to try a third party-app, our Deep Clone for Jira can clone projects and issues, including their attachments. It's as easy as checking one box in the Deep Clone configuration.

Hi @Benjamin D If you are willing to try a third-party app for migrating projects between your production and sandbox environment, you could try our Deep Clone for Jira. We have even a detailed writ up on that use case here.

Hallo @Robin Specht Kein Problem :) Wir sind auch aus Deutschland und verstehen die Limitationen der DSGVO natürlich, aber ich denke, jedes Unternehmen kann unsere Apps DSGVO-konform verwenden. Unsere Apps werden, je nach Standort der Jira Instanz, auf Servern in der EU betrieben, sogar in Deutschland, um genau zu sein.…