Julien Peyrade _ Elements Atlassian Partner

Hello @lgolden If you don't mind using an add-on, Elements Publish to Confluence lets you do exactly what you are asking. Full disclosure: I'm the Product Manager of the app. With our app you can create Confluence pages from Jira issues. It integrates with Automation, but it has many more features than the native solution.…

Hello @Yasmine If you don't mind using an add-on, Elements Publish to Confluence lets you do exactly what you are asking. Full disclosure: I'm the Product Manager of the app. With our app you can create Confluence pages from Jira issues. It integrates with Automation, but it has many more features than the native solution.…

Hello @Maggie Haefele If you don't mind testing an add-on, Elements Copy & Sync lets you do exactly that. Full disclosure, I'm the Product Manager of the app. With our app, you will be able to clone tickets from any project to any project, including subtasks with full field mappings. You can have a look at the…

Hello @Bea Tea There is no solution out-of the box. However, you can do this very simply with a Jira add-on : Elements Publish to Confluence . Full disclosure: I'm the Product Manager of the app. With our app you can create Confluence pages from Jira issues. It lets you : * insert any Jira issue data in the Confluence page…

Hello @Jim Strange If you don't mind using a add-on, Elements Copy & Sync lets you copy issues and initialize them with the status of your choosing. Full disclosure, I'm the Product Manager of the app. Basically, with our app you can : * initialize an issue with the exact same status as the original issue * initialize an…

Hello @Sakina That's a great suggestion, I will definitively take it into consideration. Thank you for your input. Julien

Don't worry, you can. As I said, there is no downside in using templates. To insert Jira data into a template, you need to use the Elements Publish macro : And then you can insert the link to the issue, just like you do in the app : Julien

@Sakina If you want to use Confluence macros, you need to create your pages from a Confluence template. There is no downside in using this option : you can create Confluence templates from scratch if you need to, and then use them in Elements Publish. You will even have access to more options, such as Confluence macros.…

Thank you for the feedback! I will definitively take this into consideration. Currently, to do this, you need to create one recipe for each possible target page, and specify on which project these recipes are available in the Source tab of the recipe.

Hello @Sakina Creating a link in the Confluence page to the Jira issue is only possible within the content of the page. If you want to insert this link in the page, you should use the "Link to source issue" option in the "Insert" menu of your recipe, and place it anywhere in your page. I hope this helps. Kind regards,…

Hello @Michael Mueller Unfortunately, it's not possible to hide the option from this menu. This is due to a Jira limitation : if we want to be able to offer this location to some of our users, we have to "declare" it upon the app installation. It's all or nothing for us here. I'm sorry, I understand this can be confusing…

Hello @Sakina If you don't mind using an add-on, Elements Publish to Confluence lets you do exactly what you are asking. Full disclosure: I'm the Product Manager of the app. With our app you can create Confluence pages from Jira issues. It integrates with Automation, but in addition to the native feature you can : * insert…

Hello @Michael Mueller Unfortunately, this is not possible with Automation as of now. However, if you don't mind using an add-on, Elements Publish to Confluence lets you do exactly what you are asking. Full disclosure: I'm the Product Manager of the app. With our app you can create Confluence pages from Jira issues.…

Hello @Maria Sol Fontenla If you don't mind using an add-on, Elements Publish to Confluence lets you do exactly what you are asking. Full disclosure: I'm the Product Manager of the app. With our app you can create Confluence pages from Jira issues. It integrates with Automation, but in addition to the native feature you…

Hello @Steven Lloyd If you don't mind using an add-on, Elements Publish to Confluence lets you do exactly what you are asking. Full disclosure: I'm the Product Manager of the app. With our app you can create Confluence pages from Jira issues. It integrates with Automation, but in addition to the native feature you can : *…

Hello @Trisha Eunice Dagohoy If you don't mind testing an add-on, Elements Copy & Sync lets you do exactly that. Full disclosure, I'm the Product Manager of the app. With our app, you will be able to clone tickets from any project to any project, including team-managed ones. You can decide which fields to copy or not,…

Hello @Dorothy Callahan If you don't mind testing an add-on, Elements Copy & Sync lets you do exactly that. Full disclosure, I'm the Product Manager of the app. With our app, you will be able to clone the issue at the end of your sprint (with all the information you could need, fields, attachments, comments... all…

Hello @Bryan Tito If you don't mind testing an add-on, Elements Copy & Sync lets you do exactly that. Full disclosure, I'm the Product Manager of the app. With our fields mapping, you can copy anything you want from an issue to another issue, including Forms. You just have to select "Jira Forms" in our Fields Mapping when…

Hello @Keven Pepin The following JQL will give you the subtasks of your Epic : linkedIssue = [ISSUE KEY OF YOUR EPIC] and issuetype = sub-task You will have to replace "sub-task" by the actual subtask type used in your project.

Hello @Florian Kniep-Eibenstein Yes, I apologize, we had a little hiccup today. Everything should work as expected now, the full Epic->Tasks->Subtasks tree will be copied by your recipe. Sorry again for the unexpected back and forth. Kind regards, Julien

Hello @Duulga Enkhtur I believe subtasks are not meant for what you need. If I were you, I would use a different issue type in place of the subtasks, and link these issues to your main task with a specific link type, such as "is blocked by". This way, all your issues could be moved and ranked independantly, while still…

Hello @Jorik Kloppenburg If you don't mind testing an add-on, Elements Copy & Sync lets you do exactly that Full disclosure, I'm the Product Manager of the app. With our fields mapping, you can copy anything you want from an issue to its copy, including the Epic link. As a bonus, you can keep this Epic synchronized, so if…

Hello @Florian Kniep-Eibenstein If you don't mind testing another add-on, Elements Copy & Sync lets you do exactly what you need. Full disclosure, I'm the Product Manager of the app, but the good news is that, as such, I'm pretty sure that we will be able to help you. We have two options called "Copy full Epic Tree" and…

Hello @Emily Eicher I apologize in advance for self-promoting, feel free to dismiss my message if needed, but I'm the Product Manager for the app Elements Publish which I know will help you with this need. With our app, you can create Confluence pages from any Jira issue, including Jira Product Discovery ideas. Where the…

Hello @Ana-Rita Silva If you don't mind using an add-on, I would suggest Elements Copy& Sync, which will let you automate the creation of subtasks (with static or dynamic values automatically populated) every time you clone one of your main three templates. I'm the Product Manager of this app (which is free for up to 10…

Hello @Russ White Team-managed projects' workflows cannot be synchronised by Elements Copy & Sync, as Jira does not use the same workflow system as regular projects, so the add-on won't be able to help you in that case. However, for other cases, the proper way to set up your Jira would be to use the same workflow for all…

Hello @Nate Jenks I'm Julien Peyrade, the Product Manager for Elements Copy & Sync. I'm glad you reached us through our Support Portal as well, and I hope you found the answer satisfactory. If you need anything else, we can continue the discussion on your ticket there. Kind regards, Julien

Hello @Aykan Inal If you don't mind using an add-on, Elements Copy & Sync lets you do just that. (It's free for instances up to 10 users.) I'm the Product Manager of the app, so I'm pretty sure that you can use it to automate subtasks creation. For example, every time a request with a given request type is created, several…

Hello @[deleted] If you do not mind using a paid add-on, I can suggest the app "Elements Copy & Sync", which was designed to resolve your exact use case. I'm the Product Manager of the app, so I would be happy to answer any question you might have. Basically, the app would let you copy your support ticket into any…

Hello @Austin Tristan As an alternative, if you don't want to be restricted by Automation limitations and don't mind using a paid add-on, I'm the Product Manager of Elements Copy & Sync, which is used precisely for use cases like yours. Our add-on has been designed to help users escalate tickets from JSM to another project…