Julien Peyrade _ Elements Atlassian Partner

Hello @Bhanu Thanks for mentioning Elements Publish! However, I must add on to your comment to say that Elements Publish is a Cloud-only app, which will not help in the case of @M Sunil Kumar . On Data Center, most of the functionalities of Elements Publish are available in our other app, Elements Copy & Sync, which might…

Hello @Konica Garg If you don't mind using an app, Elements Publish lets you do exactly what you are asking with fewer hurdles and more options than Automation. 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. Indeed, you…

Hello @Dan Allenby Correct me if I'm wrong, but what I'm understanding from your question is that you want Jira fields to be automatically pulled to Confluence pages when they are updated? If this is indeed what you are trying to achieve, we have an app called Elements Publish that allows you to publish data from Jira to…

Hello @Christian Risolia Welcome to community! If you're willing to use a third-party application, I can suggest trying our Elements Copy & Sync app that allows you to copy issues with all their content (summary, description, custom fields, comments, attachments, etc.) and their child issues. Using our feature Copy full…

Hello, When cloning a project, there are generally two primary objectives: duplicating the project's configuration or its contents - including Epics, Stories, and Subtasks - or potentially both. You can replicate the project configuration using a built-in Jira feature known as the shared project configuration. For cloning…

Hello @carl No, Elements Copy & Sync is meant to copy issues, with everything in them (fields, comments, attachments, etc.). However, when creating a Project with Jira, I do believe there is a native option to create this Project from another one, thus copying its config, workflow... I hope this helps. Julien

.

Hello @ddch.peradze I apologize for the very late answer, but since I'm not sure you got the help you needed, I'll do my best to help with an up-to-date solution. So, if you don't mind using an add-on, Elements Publish lets you do exactly what you are asking. Full disclosure: I'm the Head of Product at Elements, which is…

Hello @Luc Noppen I apologize for the belated answer, but since I'm not sure you got the help you needed, I'll do my best to help. So, if you don't mind using an add-on, Elements Publish 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…

Hello, There are two main things that one might want when cloning a project: to copy the project configuration or to copy its content (its Epics, Stories and Subtasks). Or both, of course. Cloning the project configuration can be done with a native Jira feature, the shared project configuration. However, in order to clone…

Hello, As far as I can tell, there are two aspects in using a "template project": you may want to copy the project configuration, you may want to copy its content (Epics/Stories/Subtasks), or both. The configuration part can be achieved natively within Jira, even though I believe you need to have Standard Jira instance,…

Hello, Currently, within Jira, their is no native way to clone an Epic while including its stories and subtasks, thus cloning the whole "Epic tree". To do this, I would recommend our app, Elements Copy & Sync which can help you do exactly this. Epics can be cloned in one click, including all the issues within it (and their…

Hello, I believe this question has not been fully answered, so if you don't mind I will try my best. As far as I understand, you need to initialize new projects, automatically, with specific epics/tasks and no outside action required. The answers so far seem to be for Data Center instead of Cloud, or to clone project…

Hello, This use case is quite interesting, as it's something I have quite often encountered when speaking with Project Managers using Jira. Basically, what you need is a "Template" project, which contains all the possible features or specs that will need to be often reused. This is your source of truth, that needs to…

Hello, Cloning several issues from one project to another can take a lot of time, even more when they are organized in hierarchies, with Epics, tasks and subtasks. To make things easier, I would recommend our app, Elements Copy & Sync which can help you do exactly this. We have created this short tutorial to explain how we…

Hello, Cloning issues from one Next-Gen project to another may have lead to problem when doing this with Automation, due to the issue types. What I would advice is keep using Automation to trigger the cloning, if needed (indeed, Automation has a ton of useful triggers for various needs), but leave the cloning itself to a…

Hello @Elizabeth_Johnson If you don't mind using an add-on, in addition to Automation or not, Elements Copy & Sync lets you do exactly that. Basically, what you need to do is have a "template project" with all the Epics you may want to copy with their tasks. With Copy & Sync, you can automate the copy of these Epics, with…

Hi @Kara Smith I'm pretty sure the native cloning function of Jira may be in conflict with the content of your missing subtasks. It can happen and the reason for it is often hard to pinpoint exactly. Have your tried the exact same use case with an add-on instead? Elements Copy & Sync lets you do exactly that. Full…

Hello @Nolan McConnell If you don't mind using an add-on, Elements Copy & Sync can help you do exactly this. It's free for Cloud instances up to 10 users and has a 30 days free trial for all. I'm the Product Manager of the app, so I can help you if you have any question. Among many other things, it lets you create subtasks…

Hello @Antonio Domenech Picó 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…

Hello @Dd If you don't mind using an add-on, Elements Copy & Sync can help you do exactly this. It's free for Cloud instances up to 10 users and has a 30 days free trial for all. I'm the Product Manager of the app, so I can help you if you have any question. Basically, it lets you clone issues with customised options (you…

Hello @Jehu Pineda 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…

Hello @Vlad Carballo I think this use case is what you are trying to achieve? Leverage a template project in Jira by bulk copying issues. If yes, I hope that you find the attached tutorial helpful. Kind regards, Julien

Hello @Thies Uhlenbruch I hope I'm not too late for a reply. 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. We have released, just today, the feature you need. It lets you initialize any date field with calculated values. The "work…

If you don't mind, could you create a support ticket? Our team will be happy to answer any of your question, even the hardest. :) Unfortunately I'm unable to take any call before next week.

Hello @Sara Palmitessa 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 Epics with all their issues, including subtasks and forms, and keep the hierarchy. It is as easy as clicking on two options,…

Hello @Michael Hart I agree with this other response, this process will end up quite messy. Ideally, you want your devs to only have to work in their dev projects, and your support team to stay in the Support project. If you don't mind using paid add-ons, there are several that have been created specifically for the…

Hello @James Powell-Chandler If I understand correctly you wan to automate the creation of Confluence pages each time a type of request is raised in JSM, and add information from the Jira ticket to the page? If you don't mind using an add-on, Elements Publish to Confluence lets you do exactly what you are asking. Full…

Hello @bilel_arfaoui Sorry for the belated response, I just saw your question. Yes, this can be automated fully. You can either create pages: * manually, by clcking a button on the issue * during a workflow post-function (let's say, when an issue is created or when it is transitioned to the status "in progress" * or with…

You're welcome. I understand how pricing can be a blocker in certain cases, I hope you manage to reach a satisfying solution to your problem.