Clara Belin-Brosseau_Elevatic Atlassian Partner

Hi @Nagaraja (MicroGenesis TechSoft) And thank you @Marc -Devoteam- for mentioning Elements Copy & Sync! Indeed, this is a standard use case covered by our app. You can synchronize issues across Cloud projects very easily with all their associate fields. To do so: * Create a "Synchronize linked issues" recipe * Select…

Hi @Asier Vadillo Automation rules are often prone to errors and pretty hard to maintain on the long term. It becomes even more true when you have a large number of rules running. As an alternative, I can suggest trying our app Elements Copy & Sync to manually clone issues from one project to another. It should save you a…

Indeed @Mohana Sundar Jou're right Automation could be use for some of the use cases but it has quite limitations and constraints that make it harder to use compared to Elements Copy & Sync. If you're interested the limitations are described in this article.

Hi @jrmorrison If you're open to use a third-party app, I can suggest trying our app Elements Copy & Sync. It will allow you to bulk clone your template work items in any project you'd like. Here are the steps you should follow (it only takes a few minutes to set up): * Create a project template with the recurring work…

Hi @Saif Wahab As an alternative solution to Automation that can be quite complex and limited in terms of number of executions, I can suggest trying our app Elements Copy & Sync. It will allow you to clone issues across projects based on triggers and to map fields such as the reporter field. A practical setup: Create a…

Hi @Phương Hoàng Thị Mai As an alternative to ScriptRunner, I can suggest trying our app Elements Copy & Sync. It will create the target issue and injects field values in the same operation, instead of “creating first, updating later”. These are the steps you should follow to configure the app: Create an Operation that…

Hi @Ward Schwillens_ Schwillie As previously stated in the comments, Atlassian does not provide native hierarchical issue templates. As an alternative I can suggest trying our app Elements Copy & Sync to create reusable templates of epics/tasks/subtasks. These would be the steps to follow: 1. Create a dedicated Template…

Hi @Shawn Wallace As @Robert DaSilva mentioned, the "share settings with an existing project" option is a great way to duplicate the whole configuration of a template project. If you also want to clone all the issues inside the initial JSM project, you can do so very easily by using our app Elements Copy & Sync. You'll be…

Hi @Jennifer Bormann I just wanted to offer an alternative by trying our app Elements Copy & Sync that allows you to: automatically create a ticket when a task is resolved comments are copied over from the resolved ticket to the new one Here are the steps to automatically copy comments from your source task to the newly…

Hi @AnCha Hesse Jira Automation can react to Issue A’s transition and try to transition linked issues, but only if that transition exists in their current workflow.It cannot bypass workflow rules or force a status change when the linked issue doesn’t offer that transition. As an alternative to Jira Automation, I can…

Hi @Asier Vadillo You’re correct, Jira’s native clone feature is quite limited when it comes to controlling which fields are copied. When you clone an issue using the built-in feature, Jira will copy: Summary, description, components, labels, and most system fields Custom fields (if they are standard Jira types) But it…

Hi @Cody Ouimet If Jira Automation can’t copy existing comments when cloning an issue, you can achieve this easily with our app Elements Copy & Sync which is dedicated to cloning and synchronization of Jira issues. Unlike native automation, Elements Copy & Sync lets you clone issues across projects and copy all comments…

Hi @Aidan Grey In case you haven't found a solution yet, I can suggest trying our app Elements Publish which would definitely solve your use case. Here’s how you can build a dynamic Confluence status page that automatically updates with the latest Jira issue data (like defect status or the most recent “update” comment): 1.…

Hi @thumuluru.shreya I don't know if you did find a solution to your problem but I wanted to share another way to create a Confluence page from a Jira issue with all its data. You can try our app Elements Publish to do so, it's easier to set up than an Automation rule. Here’s how you can set it up: Install Elements…

Hi @Taras Boianovskyi Welcome to the Community and thanks @Marc -Devoteam- for mentioning us. You’re right, Jira’s native automation has a limitation when it comes to copying attachments between linked issues. Even with the right permissions, automation rules can only reference or link to attachments, not actually…

Hi @Nicolas Shinozaki If you’re looking for a faster and more straightforward solution compared to Automation to clone an Epic with all its subtasks, I can suggest trying our app Elements Copy & Sync. In the app, go to Recipes → Create recipe: 1. Scope: Choose Epic as the Source issue type. Optionally restrict it to a…

Happy to read that our app Elements Publish helps you integrating Jira and Confluence together!

Bonjour @Frédéric COURBIERE Quelques pistes à explorer qui pourraient résoudre votre problème : Assurez-vous que l’adresse utilisée soit bien celle liée à votre compte Atlassian. Ajoutez l’expéditeur no-reply@am.atlassian.com ou no-reply@atlassian.com à votre liste de contacts pour éviter que le mail soit bloqué. Si malgré…

Hi @Rob Horan You’re right, Loom currently displays relative timestamps rather than absolute dates and times, trust me I do share your frustration! At the moment, there isn’t a built-in setting to switch to real (absolute) dates in Loom’s interface. A couple of small workarounds that can help: Hover over the relative…

I'm pretty sure you're not the only one to encounter this issue, that's why bringing it to Trello support team will probably help prioritizing the resolution.

Of course I understand, these were workarounds rather than long-term solutions. I think the best way is to reach out to Trello support team!

Hi @Bethany Carter You can absolutely set up automated recurring tasks in Jira using our app Elements Copy & Sync It lets you automatically clone issues (including fields, attachments, subtasks, and comments) whenever you need them: for example, every month or when a task is completed. You can also predefine where the…

Hi @Puru If you want each team to work on their own issue while maintaining a master view automatically, you can use our app Elements Copy & Sync.It lets you: Automatically clone issues when moved or transitioned. Sync statuses, comments, or fields between the original and the clone. Keep a single “overview” issue or board…

Hi @Dino, It sounds like you’re running into two separate issues: one with duplicated images when pasting into comments, and another with the readability of the new layout. 1. Duplicate images when pastingThis is a known behavior some users have reported since recent Trello updates. It typically happens when pasting images…

Hi @David Ortiz Bollain If you can't make it happen natively, I can suggest trying our app Elements Copy & Sync that allows you to clone Jira epics (you can even include the child issues). You can clone any Epic or set a status like "Done" for example. Don't hesitate to try it (it's free for 30 days).

Hi @Carlos Morell Welcome to the Atlassian Community! When you clone an issue in Jira, only the text data (summary, description, comments, etc.) is copied by default. Attachments and inline images in the description are not fully duplicated: the new issue’s description still references the original file paths, but those…

Hi @Luke Jackson As an alternative to Automation (that can be pretty complex sometimes), I can suggest having a look at our app Elements Copy & Sync. It allows you to clone work items from one project to another and link them together. The configuration only takes a few minutes and then you won't have to do anything…

Hi @Selvaggia Cerquetti I can suggest another way to easily clone your template without the unnecessary subtasks. You can have a look at our app Elements Copy & Sync: it allows you to clone Jira issues with any field you'd like (attachments, child work items, links in your case). You'll have the option to clone the…

Hi @Abri Buys If you’re looking for a faster and more straightforward solution compared to Automation to escalate an issue from Jira Service Management to Jira, I can suggest trying our app Elements Copy & Sync. You’ll be able to perform the following steps automatically and within one single configuration: * Clone the JSM…

Hi @Witt, Laura Kristin (MRB-R) In the new Jira board, cloned issues land in the backlog by default. If you want more control, you could our app Elements Copy & Sync: it lets you build templates and configure them so that when you create a copy, it automatically inherits the right status. This way you don’t need to…