Luka Hummel - codefortynine Atlassian Partner

Hi @robyn.graham I'm sorry you are having trouble with Deep Clone. Could you please submit a support request here so we can take a closer look at the problem?

Hi @Fahim Ahmed I'm Luka from codefortynine 👋 If you are willing to try a third-party app, our Deep Clone for Jira can help you clone your issues between your Jira Service Management and Jira Software project. We have written a guide for 'escalating tickets' which should fit your use case quite well here. As long as you…

Hi @Bente and welcome to the community 👋 As @Aron Gombas _Midori_ was so nice to mention, you can try our app Deep Clone for Jira. Deep Clone can clone your template project with its Project Clone feature. You can find a detailed step-by-step in our documentation here. If you want to change dates, or other custom fields,…

Hi @Erik Mathijs I'm Luka from codefortynine 👋 If you are willing to try a third-party app, you can try our app Deep Clone for Jira. Deep Clone can clone your template project including all subtasks with its Project Clone feature. You can find a detailed step-by-step in our documentation here.

Hi @michael_glenn_williams I'm Luka from codefortynine 👋 If the native cloud-to-cloud features of Jira are not sufficient, and you are willing to try a third-party app, our app Deep Clone for Jira can help you migrate your issues between instances with our Instance Clone feature. It's a common use case for Deep Clone, and…

Hi @margolles If you are willing to use a third-party app, our app Deep Clone for Jira can help you with your use case. To achieve your goal with Deep Clone you can create a template epic with all its children and then use our Epic/Tree Clone feature to replicate the template whenever you want. 

Hi @Sasha I'm Luka from codefortynine 👋 It's impossible to clone issues from team-managed projects to company-managed projects without third-party apps. Our app Deep Clone for Jira can clone from team-managed to company-managed, and vice versa. If you want to trigger Deep Clone via a Jira automation, you can also do that…

Hi @Eric Jahn I'm Luka from codefortynine 👋 This happens because cloning in Jira creates a new issue with the default status of its workflow, rather than directly copying the status of the original issue. To address this, you could consider a two-step process in your automation: * Clone the Sub-task: First, clone the…

Hi @Kristaps I'm Luka from codefortynine 👋 If you are willing to use a third party app, you might be interested in our Deep Clone for Jira. We just added the ability to configure how Deep Clone handles schemes when cloning a project.

Hi @Giovanni Lancianese I'm Luka from codefortynine 👋 If you are willing to try a third-party app, you could try our app Deep Clone for Jira. With Deep Clone for Jira, you can: * Clone Attachments: Easily clone attachments from the original issue to the new one. * Bulk Clone: Clone multiple issues at once, including their…

Hi @Andrew Wursta and welcome to the community 👋 I'm from codefortynine and if you are willing to try a third party app our app Deep Clone for Jira can help you clone your issues including comments. Although like @Trudy P Claspill already mentioned it's currently impossible to clone the issue history of an issue.

Hi @Karen If you are willing to use a third party app, you might be interested in our Deep Clone for Jira. We just added the ability to configure how Deep Clone handles schemes when cloning a project.

Hi @Dominika Włodarczyk and welcome to the community 👋 Creating using the CSV import function for template issue hierarchies (Initiative → Epic → Task/Story → Subtask) can be quite finicky. Our app Deep Clone for Jira can help you replicate your template hierarchies really quickly and efficiently. With our Epic/Tree Clone…

Hi @M. Gabriela Labastidas If you are willing to use a third-party app, you could try our app Deep Clone for Jira. While the primary function of Deep Clone is to clone issues and their configurations, it can also be used creatively to achieve a template-like functionality for sub-tasks and bug tasks. Here’s how you could…

Hi @Arthur Harutyunyan Thank you for your praise and for also contacting our support. I will add my answer also here, so others can find it if they encounter a similar problem. It’s theoretically possible, but the source project needs to fit specific requirements. If you didn’t consider this when creating the project, it’s…

Hi @Dale Bronk I'm Luka from codefortynine 👋 If you are willing to use a third-party app, our app Deep Clone for Jira offers a suitable solution. Deep Clone allows for advanced features not available in the standard Jira clone function. Specifically, it enables you to edit the issue type for both single and bulk clones​​.…

Hi @Ashish Bajaj I'm Luka from codefortynine. If you are willing to use a third-party app, our app Deep Clone for Jira can make it easy to move your issues between projects using Jira automations. Deep Clone allows for the integration with Jira Automation through the use of post functions and global looping transitions.…

Hi @Luis Portela and welcome to the community! If you are willing to use a third-party app, our app Deep Clone for Jira can help you to set up your new project and also can enable you to use template issue hierarchies (e.g., Epics). Deep Clone can help you to clone your issues from your old 'client' projects to your new…

Hi @Andrew If you are willing to use a third-party app, our app Deep Clone for Jira can help you when working with template issues. You can create your template issue or even a whole issue hierarchy (Epic → Task/Story → Sub-Task) and then clone it with all its field values whenever you need with Single Clone or Epic/Tree…

I began immersing myself in the community in 2023, a journey that has been incredibly rewarding. A standout moment was certainly attending Team '23 in Las Vegas, where I had the opportunity to engage with some community members and explore the whole ecosystem firsthand. Moreover, each time one of my answers is accepted,…

Hi @apoage and welcome to the community! I'm Luka from codefortynine 👋 If you are willing to use a third party app, our app Deep Clone for Jira can help you with automating your issue cloning. While we don't support scheduled clones (yet) our app integrates with Jira Automation, enabling you to set up automated workflows…

Hi @Neeta Dubey Glad our app could help you! We currently want to give the user the ability to stop after cloning the project without cloning any issues. This is a common use case for people that need to set up empty projects according to an already defined configuration. Thank you for your feedback! I do understand that…

Hi @Neeta Dubey I'm Luka from codefortynine 👋 If you are willing to use a third-party app our Deep Clone for Jira offers a robust solution for your needs. It is designed to work seamlessly with Atlassian Cloud and can help you clone an entire project, including all its tickets (issues). Here’s how Deep Clone can assist you…

Hi, I'm Luka from codefortynine 👋 I also want to add that you can use our app Deep Clone for Jira to clone template projects and issues. Deep Clone can clone a project, including its configuration with Project Clone. Additionally, you can also clone template Epic hierarchies or other hierarchies with Epic/Tree Clone. You…

Hi @Arthur Harutyunyan I'm Luka from codefortynine the creators of Deep Clone for Jira 👋 Thanks to @Ste Wright for mentioning us! I think most points in your use case can be solved within Deep Clone without any need for additional Jira automations. 1) You should be able to change the issue type while cloning. 2) Deep Clone…

Hi @Sduvvuri and welcome to the community! I'm Luka from codefortynine 👋 As @Mykenna Cepek already mentioned, there are solutions for your use case in the Marketplace. Our app Deep Clone for Jira allows you to clone Epics and all their linked issues with its Epic/Tree Clone feature, including Stories. This ensures that the…

Hi @Sai I'm Luka from codefortynine 👋 If you are interested in cloning Issues between a sandbox and a production Jira Cloud instance, you could use our app Deep Clone for Jira. This is possible thanks to our Instance Clone feature, allowing you to clone Issues across instances. There is also a more elaborate guide here.

Hi @Montnic I'm Luka from codefortynine 👋 I understand the frustration with encountering an error when trying to clone to Project B. If you are willing to use a third-party app, our Deep Clone for Jira could help you. In this context, Deep Clone for Jira could be a highly effective solution. Deep Clone is designed to…

Hi @ayoung If you are willing to use a third party app our Deep Clone for Jira could be a useful alternative for you. Deep Clone simplifies the cloning process, including the ability to clone custom fields without needing to know their specific IDs. Here's how Deep Clone can assist you: * Custom Fields: When cloning an…

Hi @Nico Chen and welcome to the community! Your idea of having a template to create new projects is spot-on, and I have good news for you: Deep Clone for Jira can help with exactly that! Deep Clone for Jira allows you to clone not just issues but entire projects including all of their configurations with Project Clone.…