Clara Belin-Brosseau_Elevatic Atlassian Partner

Hi @Ekra Hossain Picking up on the bulk cloning angle mentioned in this thread: our app Elements Copy & Sync offers this too. You set up a recipe once, point it at a JQL search result, and it clones all matching issues in a single run instead of one by one. What makes it a bit different from a straightforward clone tool is…

Hi @King_ Lee As others already mentioned, Jira doesn't support bulk cloning natively. As an alternative I can suggest trying our app Elements Copy & Sync. The app supports bulk cloning of Jira issues: you run a recipe against a JQL search result and it clones every matching issue in one go, rather than cloning one at a…

Hi @AS If you want an easier alternative to do this, our app Elements Copy & Sync can handle this kind of cross-project workflow. The app allows to automatically clone Jira issues from one project to another and keep them synchronized if needed. These would be the set up steps: * You create a "Copy and Synchronize work…

Hi @Federico Frade Sounds like you managed to solve your problem! One thing worth mentioning: if you ever need comments to be synchronized between tickets to avoid manual updates, that's where our app Elements Copy & Sync can help. Instead of only cloning comments and fields once, it can also keep them…

Hi @cvanduyn As an alternative to Automation, you could try our app Elements Publish instead. It's built for this exact use case: you can automatically create a Confluence page from a Jira issue and insert any field directly into the page, including inside a Confluence template body (something Automation currently can't…

Hi @J B, Good to hear the native "Create work item" action solved the attachment copying for you. One thing worth mentioning for this kind of escalation workflow: if you ever need the connection between the Support ticket and the DEV ticket to stay live (not just a one-time copy at creation), that's where our app Elements…

Hi @Dominik Boehm, This is a common limitation with native Jira Automation, when you "create issue" or "clone" across projects, some fields (like Assignee) don't always carry over cleanly, especially when the value depends on a custom field selection rather than a direct mapping. If you want a more reliable way to handle…

Hi @kshridvipa7878 As an alternative I can suggest trying our app Elements Copy & Sync. The native bulk move can work, but it has limits on very large volumes and doesn't give you much control over field mapping between a Kanban and a Scrum scheme. Elements Copy & Sync lets you move a full hierarchy of Jira issues from…

Hi @Chan_ Renee For this kind of use case (inserting a batch of Jira tickets data into a Confluence page, including attachments like screenshots), you might want to look into our app Elements Publish. It's built specifically to generate Confluence pages from Jira tickets, and it does carry over attachments/screenshots…

Hi @mkurdi As an alternative to the native cloning feature which can be limited in terms of granularity and flexibility, I can suggest trying our app Elements Copy & Sync. You have the option to clone work items with or without the attachments: You can do the same with comments or any other field. You can check the…

Hi @Negar Jalalian Cloning scenarios like this one are notoriously difficult to achieve with native Automation rules, you're definitely not the only one who's struggled with this! As an alternative, I can suggest trying our app Elements Copy & Sync. It handles this kind of use case very well. It allows you to clone a…

Hi @Vani Jayanthi I just wanted to provide an alternative to Automation here that can be sometimes rather difficult to maintain over time. I work for Elements Copy & Sync and many people use the app to solve the exact same use case as yours, meaning bulk cloning Jira issues and changing their work item type at once. The…

Hi @Bridget Caci In case you need an quicker solution to clone a set of issues from one projet to another, I can suggest trying our app Elements Copy & Sync. It lets you clone Jira issues from one project to another super quickly and efficiently through preconfigured recipes. It only takes a few minutes to set up and…

Nice to see how app editions have been evolving across the Marketplace over the past months. At Elements, we’ve also rolled out editions for Elements Copy & Sync and Elements Connect. It gives us more flexibility to better align with the different needs we see across teams, from simpler setups to more advanced use cases.…

Hi @Alex S As an alternative to Automation that can be rather complex and rigid sometimes, I can suggest trying our app Elements Publish. It's mostly used for similar use cases as yours. This is what the app can do: * Automatically create a Confluence page from a Jira ticket (compatible with Automation) * Insert Jira issue…

Just stumbled upon this article, very interesting, lots of practical questions and real-life use cases covered. From our side, we’ve seen many teams get additional value by combining Automation with our apps Elements Copy & Sync and Elements Publish. Automation is actually a great way to trigger app configurations, for…

Hi @abalog If you're still trying to link Jira tickets to Confluence, I suggest trying our app Elements Publish. It's used by our customers to track tasks and projects in Confluence but also to automate documentation creation. Basically what the app does is: * Automatically create a Confluence page from a Jira issue *…

Hi @Венера Automation can sometimes be rather tricky so I wanted to suggest an alternative: our app Elements Copy & Sync. The app allows you to clone a work item from project A to project B, to copy field values and even copy your Assets field. You simply has to create a "Copy and synchronize work items" recipe and map the…

Hi @Stephen Anderson I don't know if you managed to solve your use case with Automation but it's true that it can be sometimes rather complex to set up and afterwards, to maintain. Our app Elements Copy & Sync was actually built to deal with this kind of use case: you can easily set up a configuration that clone a ticket,…

@Katrina Thacker the licensing is based on the Jira licensing tier. You can check it out here.

Hi @Manor Shaked Schlossberg I wanted to suggest an alternative solution to collaborate on the same case but on different work items: you can try our app Elements Copy & Sync. The configuration is very simple and it will allow the cloning of your JSM work item into a Jira bug ticket (with all the fields needed). Both team…

Hi @Katrina Thacker Yes of course, the user will access all the Jira data displayed in the Confluence page wether he has a Jira licence or not :) 

Hi @Si Scott I can suggest trying our app Elements Copy & Sync to automatically create subtasks for your releases. It only takes one single configuration and is very easy to set up. Here are the steps: * Create a recipe called "Create subtasks from a source issue" 2. Define your source and target spaces 3. Define which…

Hi @Lukas Pernpeintner In case you didn't find an easy way to solve this yet, I can suggest trying our app Elements Copy & Sync to both clone an issue from project A to project B and keep their fields synchronized. One single app does everything in a unique configuration so it should only take you a few minutes to set up.…

Hi @Kathleen Hamilton Automation can be quite tricky and hard to maintain when it comes to cloning issues from one project to another along with all the subtasks. It will probably require multiple rules to achieve a satisfying result or at least a rather complex workflow. As an alternative to both facilitate and automate…

Bonjour @Sarah Lloyd Sur Trello vous avez des options de formatage assez basiques, vous pouvez utiliser le format Markdown pour formater le texte dans les descriptions et commentaires des cartes. Par exemple: Gras : **texte** Italique : *texte* Barré : ~~texte~~ En revanche il me semble que le soulignage par exemple n'est…

Great, don't hesitate if you have any question :)

Hi @Alex Cook I wanted to suggest you an alternative to Automation that should help you get that use case implemented easily. Our app Elements Copy & Sync is often used by our customers to create recurring tickets for projects that repeat themselves. In the app you can configure everything in the same place: * Define…

Hi @Marigona Alimi As @Bill Sheboy mentioned earlier, if Automation is too much of a struggle, you can use a marketplace app to clone epics with their child issues in a new project. I work for Elements Copy & Sync which is an app dedicated to the cloning and syncing of work items in Jira. You can clone any type of work…

Hi @Sathish Kumar As an alternative to the native macro which can be limited (only a table but not a proper way to insert fields in your page), I can suggest trying our app Elements Publish to insert Jira work items into a Confluence page and keep them in sync. It's very simple to set up: * Install the app on your instance…