Luka Hummel - codefortynine Atlassian Partner

Hi @František Vůjtek This might be caused by some issues with the API Atlassian is using. We have encountered similar problems when upgrading our app to the REST API version 3. If you don't want to wait for Atlassian to fix this and are willing to try a third-party app, our app Deep Clone for Jira can clone issues with…

Hi @Bernd Gurn If you are willing to try a third-party app, our app Deep Clone for Jira provides a powerful solution for automating and customizing issue cloning, including pre-editing fields before cloning. With Deep Clone for Jira, you can: * Use the Field Editor to modify specific fields automatically when cloning a…

Hi @Varsha Mungale If you want to configure fields when cloning Jira tickets, our app Deep Clone for Jira offers a powerful solution. With Deep Clone for Jira, you can customize and automate field configuration during the cloning process. Here are some key features: * Field Editing: You can use the Field Editor to…

Hi @michaelreiff If you need to move Jira issues from one site to another, and are willing to use a third-party app, our app Deep Clone for Jira can make this process efficient and straightforward. With Deep Clone's Instance Clone feature, you can clone issues, including comments, attachments, work logs, and custom fields,…

Hi @Josh Allen If you're looking for an immediate solution to clone the description correctly you can try our app Deep Clone for Jira. You can integrate Deep Clone into your Jira automation to streamline repetitive tasks without compromising on detail.

Hi @Marc Mitchell If you're looking to copy forms from one Jira project to another, our app Deep Clone for Jira offers a powerful solution. With Deep Clone, you can easily clone issues—including custom fields, comments, attachments, and more—across projects. While Jira’s native automation has limitations in transferring…

Hi @Nico Van Hoof and welcome to the community! Since Jira automation doesn't support directly moving issues, your current clone-and-delete method is a common workaround. If you are willing to try a third party app, our app Deep Clone for Jira offers a powerful solution here. It allows you to clone issues across projects…

Hi @Andrew Zajicek and welcome to the community! If you're open to an alternative solution, I highly recommend Deep Clone for Jira. With Deep Clone, you can configure Post Function Clones that avoid looping issues by offering detailed control over the cloning process. You can: * Add conditions to the transition to ensure…

Hi @Valerie Vliegen If you're looking to speed up the process of creating multiple tickets for different customers, our app Deep Clone for Jira offers a powerful solution. With the Bulk Clone feature, you can efficiently duplicate issues and adjust key fields like the reporter, without triggering notification emails to the…

Hi @Colleen Cosgrove If you're looking to automate the process of cloning a ticket to another project and setting a specific link type, our app Deep Clone for Jira can streamline this task efficiently. With its Post Function Clone feature, you can integrate cloning directly into your workflows, allowing your support team…

Hi @Colleen Cosgrove If you're looking to clone a ticket on transition and need to handle required fields in the new project, our app Deep Clone for Jira could be a great solution. Unlike standard Jira automation, which doesn't allow user prompts during transitions, Deep Clone offers more flexibility. With Deep Clone's…

Hi @Zach Taylor You are correct. The secret is missing. This appears to be recently added by Atlassian. Luckily, you can simply add the secret to the URL path in this format: [Webhook URL]/[Secret] I updated the documentation to reflect this change.

Hi @Albert-Jan If you think we can do better to help convince your admin you can always contact us here. All feedback is welcome :)

Thanks for the praise :) 2. To limit the ability to comment, you can edit the status you are using for the original issue after cloning. * Go to Project Settings > Workflow (The one that is associated with the request type and issue type) * Edit > Click on the relevant status > Properties * Add the following * Property…

Hi @Zach Taylor Thank you for using Deep Clone for Jira! I can help you with your first challenge. You can use Deep Clone to delete the issue after cloning. We have created a relatively detailed guide how to do that here. Alternatively can just use multiple "Re-fetch issue data" actions. Each should delay the automation by…

Hi @Albert-Jan and welcome to the community! It sounds like you're trying to clone a Jira Service Management (JSM) ticket to another project while ensuring that the form fields, along with the values entered by the customer, are retained. Jira Automation has some limitations when cloning JSM tickets, especially when it…

Hi @Peter Niehues and welcome to the community! Cloning a business project in Jira natively is not possible, but you can achieve this efficiently with our app Deep Clone for Jira. Deep Clone allows you to: * Clone entire projects, including issues, fields, and comments. * Bulk clone multiple issues at once. * Clone across…

Hi @David Merino, If you're willing to use a third party app using our app, Deep Clone for Jira, offers you the flexibility to clone projects or issues while maintaining consistent data integrity. Deep Clone can clone whole projects including its configuration and schemes across instances.

Hi @Michael McCullough and welcome to the community! It sounds like you're looking for a way to copy projects (along with boards and their associated data) from one Jira site to another. I recommend considering our app Deep Clone for Jira, which simplifies this process significantly. With Deep Clone, you can clone entire…

Hi @Luis Zapata If you frequently perform bulk operations, consider using our app Deep Clone for Jira. It allows you to clone issues, including subtasks, custom fields, and descriptions, saving time and effort. Using Deep Clone, you can set up templates for tasks with pre-defined structures and import them as needed…

Hi @[deleted] There is currently no way for our app to utilize the native 'move' feature. Could you elaborate why cloning the issues with Deep Clone and deleting the old issues afterward doesn't meet your migration use case? It might even be the safer option as if something goes wrong you still have the original issues.

Hi @Łukasz Parafiniuk and welcome to the community! If you're looking to streamline the process of cloning child issues and assigning them to a new parent epic, I highly recommend checking out our app Deep Clone for Jira. With Deep Clone, you can: * Epic/Tree Clone: Clone entire issue hierarchies, including all child…

Hello @Bastian Schäferling and welcome to the community! If you’re looking for a straightforward solution to clone entire projects, our app Deep Clone for Jira can help. Deep Clone allows you to: * Clone entire projects with all their configurations. * Duplicate issues, including custom fields, comments, and attachments. *…

Hi Mat and welcome to the community! Our app Deep Clone for Jira could be an excellent solution for your needs. Here’s how Deep Clone can help: * Bulk Clone: You can select the 23 Stories (e.g., GRC-108 to GRC-131) as a group (or just create a filter) and clone them quickly in the future. * Link cloned issues to Epics:…

Hello @Anne van Susteren-Finger If you’re looking to move or copy a project to a new Jira instance, our app Deep Clone for Jira can make this process significantly smoother. Deep Clone is a highly versatile app for cloning Jira issues, including bulk cloning capabilities and the ability to clone entire projects. Here’s how…

Hi @Corrine Erickson and welcome to the community! If you’re looking for an efficient way to duplicate entire Jira projects, including their issues, configurations, and workflows, I highly recommend our app Deep Clone for Jira. Deep Clone is designed specifically to address needs like yours, providing a seamless solution…

Great to hear! Let us know if you encounter any roadblocks.

Hi @Ashleigh Hamilton If you're encountering errors while attempting to clone or create issues using Jira automation, our app Deep Clone for Jira, could significantly streamline your process. With Deep Clone, you can reliably clone issues across projects, including all fields, attachments, and issue types, while bypassing…

Hi peter.dangela@vista.com and welcome to the community! If you're looking to clone an entire project board with its issues, Deep Clone for Jira by codefortynine is the perfect solution with its Project Clone feature. Deep Clone also allows you to clone multiple issues, including their fields, comments, attachments, and…

Hello @ckopanon, Jira's native functionality does not support this feature. However, you can achieve this and much more using our app Deep Clone for Jira. With Deep Clone, you can: * Add and modify fields, including custom fields, during the cloning process with the Field Editor feature. * Clone multiple issues, sub-tasks,…