Clara Belin-Brosseau_Elevatic Atlassian Partner

Hello @Ghata Singhal I feel this solution could work to solve your use case: * First step is to automatically clone the issue from Instance A to Instance B * Second step is to automatically keep the two issues in sync so that they are bot updated every time there is a change You can do this really easily by using our app…

Hello @[deleted] and welcome to the Atlassian Community! Maybe this other question could help you: https://community.atlassian.com/t5/Jira-questions/How-to-sync-between-two-non-connected-Jira-instances-working-on/qaq-p/1273586 

Hello @brandon geick, Maybe this other question could help you: https://community.atlassian.com/t5/Jira-questions/How-to-sync-between-two-non-connected-Jira-instances-working-on/qaq-p/1273586 

Hello @rykiel, If you're seeking for an easy way to clone issues from one Jira instance to another, I suggest trying our app Elements Copy & Sync that allows you to clone Jira issues with all their content (summary, description, custom fields, comments, attachments, etc) and keep them in sync. You can check our guide here.…

Hello @Lynnette Akamine As an alternative to Automation (that can be complex sometimes), I would suggest trying our app Elements Copy & Sync to clone issues with their attached forms. The configuration is really simple, you can check the guide here. The app is for free during 30 days (and it stays free under 10 users).

Hello @Christine and welcome to the Atlassian Community! As an alternative to Automation (that can be really complex sometimes), I would suggest trying our app Elements Copy & Sync to move a Jira issue from one project to another. The configuration is really simple, you can check the guide here. The app is for free during…

Hello @n0216209 If I understand correctly, you’re trying to clone an issue from JSM to Jira Software, right? In that case, I would recommend trying our app Elements Copy & Sync that allows you to clone and sync a full hierarchy of issues with all their content (summary, description, custom fields, comments, attachments,…

Hello @Matthew Choi As an alternative to Automation (that can be complex sometimes), I would suggest trying our app Elements Copy & Sync to clone the Jira issue from project A to project B and keep all the fields in sync. The configuration is really simple, you can check the guide here. The app is for free during 30 days…

@Matthias Gaiser _K15t_ yes you're right, my bad, totally missed out this information! Indeed Elements Copy & Sync only works for Jira

Hello @Luigi Giancristofaro If you're seeking for an easy way to keep two issues in sync across different boards I suggest trying our app Elements Copy & Sync that allows you to clone and sync a full hierarchy of issues with all their content (summary, description, custom fields, comments, attachments, etc). My…

Hello @Ana, On the free plan, Jira and Confluence can be connected using application links, which allow you to link Jira issues to Confluence pages and vice versa. However, some features like automation between the two may be limited. To set it up: * Go to Jira settings > Products > Application links. * Enter your…

Hello @Tatiana Dubberstein If you still didn’t find a solution to your problem, I can suggest trying our app Elements Copy & Sync to clone issues across projects and synchronize them together. You can check the guide here. The app is for free during 30 days (and it stays free under 10 users).

Hello @Alexander Kolev and welcome to the Atlassian Community! Do you mind sharing a screen capture of your request type screen edition?

I'm glad you found a way to make it work (and hope it won't keep you up at night anymore!) :)

Hello @Andy If I understand correctly, you’re trying to clone a story and its linked stories as well, right? I have a solution that might answer your specific use case. You can try our app Elements Copy & Sync as following: 1. Create an Elements Copy & Sync recipe to clone your story 2. Create an Automation rule to call…

Hi @Edward Dixon and welcome to the Atlassian Community! There is no hard limit in JSM Cloud on the number of projects. However, performance can be impacted as the number of projects grows, particularly with complex configurations like custom fields and workflows. The more projects you have in your instance the more…

Hello @Pulkit Gupta If I understand correctly, you’re trying to clone only specific issue fields, right? In that case, I would recommend trying our app Elements Copy & Sync that allows you to clone and sync a full hierarchy of issues with all their content (summary, description, custom fields, comments, attachments, etc).…

Hello @Ross Heatley As an alternative to Automation (that can be complex sometimes), I would suggest trying our app Elements Copy & Sync to clone the Jira issue, link them together and then sync their status (both ways). The configuration is super simple, you can check the guide here. The app is for free during 30 days…

Hello @Nathan Yam A very easy and efficient way to link both cloned issues to the source trigger issue is to use our app Elements Copy & Sync. It automatically clones issues and define links between them. You can check the guide here. The app is for free during 30 days (and it stays free under 10 users). Let me know if you…

Hello @Nathan Yam As an alternative to Automation (that can be complex sometimes), I would suggest trying our app Elements Copy & Sync to manually clone issues to another project. It allows you to clone Jira issues with all their content (summary, description, custom fields, comments, attachments…). You can even sync the…

Claro, entiendo! Si encontra una solución nativa en Jira dejame saber porque, de memoria, no me parece posible.

Hola Sandra, Si entiendo bien su pregunta, quiere clonar épicas con todas sus sub-tareas en otro proyecto. Quiere también tener la opción de clonar las sub-tareas o no. De lo que veo, me parece complicado hacerlo con Jira Automation. Lo que le propongo es probar nuestra app Elements Copy & Sync con la cual puede crear 2…

Hello @Nathan Yam In case you need an alternative to Automation (that can be complex sometimes), I would suggest trying our app Elements Copy & Sync to clone tickets with their comments. It's automated and easier to set up. It allows you to clone Jira issues with all their content (summary, description, custom fields,…

Hello @Lejla Delic If you’re looking for a quick and easy way to clone epics with their child issues I can suggest trying our app Elements Copy & Sync. You’ll be able to clone a full hierarchy of issues with all their content (summary, description, custom fields, comments, attachments, etc). You can check the guide here.…

Hello @marianna_taborda As an alternative to Automation (that can be complex sometimes), I would suggest trying our app Elements Copy & Sync to clone issues in Jira. It's automated and easier to set up. It allows you to clone Jira issues with all their content (summary, description, custom fields, comments,…

Hello @NoName As an alternative to Automation (that can be complex sometimes), I would suggest trying our app Elements Copy & Sync to clone issues in Jira. It's automated and easier to set up. You’ll have the ability to select which field should be cloned. The app allows you to clone Jira issues with all their content…

Hello @Irina Murisic I definitely agree with Susan and Kris about the shared settings option. In addition to it, I would recommend trying our app Elements Copy & Sync to clone all the issues from your original project to the new one. You'll be able to clone a full hierarchy of issues with all their content (summary,…

Hello @Leonardo Zevallos Guzman Thanks @Josh Costella for mentioning Elements Publish, indeed, it could be a good solution for this use case. If I understand correctly @Leonardo Zevallos Guzman, you’re trying to insert Jira issue fields in your custom Confluence template, right? In that case, I would recommend trying our…

Hello @Clayton To answer your question about cloning entire projects and related issues, if that’s something you need to do, I would recommend using our app Elements Copy & Sync that allows you to clone and sync a full hierarchy of issues with all their content (summary, description, custom fields, comments, attachments…).…

Hello @Matthew Cozzi I don’t know if you found a solution to your problem but if not, I suggest trying our app Elements Copy & Sync that allows you to clone and sync a full hierarchy of issues with all their content (summary, description, custom fields, comments, attachments, etc). You’ll be able to clone your issues…