Julien Peyrade _ Elements Atlassian Partner

Hello @melina_scholl As indicated earlier by another user, the permission you are looking for is the Browse project one, which must be enabled on your Jira Software project (where the tickets are dusplicated). As an alternative, if you don't want to change the permission scheme of your instance and don't minde using a paid…

Hello @Cheng Peng I just tested and it seems to work for me, even when copying from Jira Service Management to Jira Software. Did you enable the option "Copy attachments" when you created the issue? However, I don't think it's possible to copy comments this way. If you don't mind using a other add-on, there are several…

Hello @ST Kambor-Wiesenberg Here is the automation rule, I just checked and it works perfectly : 

I have no way to check right now, but I believe something like this will work: - Trigger: When an issue is created - Loop on all the links in the issue - If link type = "clones", remove link

You were wondering about the advantage and a number of clicks, I just answered.

Hello, The plugin can be set up so that you only have to configure it once. I'm not sure of the use case during which you need to clone your issues, but if needed, you could clone them automatically during a status transition (let's say when the issue is transitioned to "In Progress"), with no additional click required.…

Hello @ST Kambor-Wiesenberg If you don't mind using a paid add-on, their are several ones that lets you create cloned issues without linking them to the original issue : Marketplace search. I'm actually the Product Manager of one of those apps, Elements Copy & Sync. Our add-on actually let's you clone and move your issues…

Great, don't hesitate if you need any help.

Hello @nicolaspannetier If you don't mind using a paid add-on, another solution would be to use Elements Copy & Sync, which lets you do just what you need. In addition to the initial copy, you would be able to synchronise the labels (or anything, actually) from the Epic to its child issues, meaning that if you add a label…

Can you see the "Parent Link" field in the "Custom fields" page of your Jira admins? If it's not there, something's wrong. If it's there, you should be able to see on which Screens the field is available, and probably make it appear on your Epics from there.

The Parent Link field is in the Epic, not the Initiative. :)

Hello @Samuel Bar There is an additional step you're missing. You need to go to the Hierarchy levels page and put you Initiative above the Epic, like this : Once this is done, you will be able to see the Parent Link field. Kind regards, Julien

Hello, No, I didn't mean create the issue during the creation of the Epic. I meant that if you want to create an issue in Epic A, this issue has to be created by clicking on a button in the Epic A. Basically, what I want to say is that you wouldn't be able to create the issue and only then add it to the Epic. You have to…

Hello @François Dumas I may have a solution, depending on how you create your issue. I'm the Product Manager of the add-on Elements Copy & Sync, which lets you do just what you need. With this plugin, the easiest way would be to trigger the issue creation from the Epic, in which case the link to the Epic, as well as the…

You're welcome, happy that you're happy. :)

Hello @Megha P Another solution would be to use the add-on Elements Copy & Sync, which I think lets you do just what you are asking. I'm the Product Manager of the app and I would gladly answer any question you might have. I'm just unsure of where your Bug is created from at the beginning. If your bug is created from…

Hello @chepec81 If you don't mind using a plugin, the add-on Elements Copy & Sync lets you do just that. Basically, you could have your developer work on a totally different issue (let's say, in a software development project) and comment there, and have all their comments be automatically synchronised to the task created…

Hello @Srujan kumar Another solution would be to use the add-on Elements Copy & Sync, which lets you do what you are asking for. An advantage of the Copy & Sync is that, in addition to cloning issues, it also copies Attachments between the two issues, which is not possible with Automation. I'm the Product Manager of the…

Hello @Lavanya B I'm the Product Manager of Elements Copy & Sync, which is an add-on that let's you do just that. Basically what you can do is enable a Copy & Sync operation that would clone your issues only for a given project. It would be completely invisible in any other project. Don't hesitate to ask our support if you…

Hello @Peter Yoon If you don't mind using a paid add-on, there is a way easier way to create a Confluence page from a Jira ticket automatically for your step 2. I'm the Product Manager of Elements Publish to Confluence, which is an add-on that lets you create a full template of the Confluence page you want to create,…

I understand perfectly. :)

Hello @Ammar Ahmed Butt Another solution would be to use the add-on Elements Copy & Sync, which lets you do what you are asking for. An advantage of the Copy & Sync is that it also copies Attachments between the two issues, which is not possible with Automation. I'm the Product Manager of the app, and would gladly answer…

Hello @Guy Mandel If you don't mind using another app, another solution would be to use the add-on Elements Copy & Sync, which lets you copy all kinds of fields, including cascaded select lists. I'm the Product Manager of this add-on which is available on Jira Cloud and Server/Data Center, and I'll gladly answer any…

Glad you already have the add-on, it will be even faster. :) Yes you can use Copy & Sync to copy data from an Initiative to an Epic, for this you just have to use the "Advanced Roadmaps" links in you operation and synchronisation configuration. This compatibility was introduced with version 3.0 of the app, so make sure you…

Hello @Vignesh Singh I'm not sure about your add-ons, but if you don't mind trying another one I can help you. I'm the Product Manager for the add-on Elements Copy & Sync, which lets you do just what you need. What we can help you with is synchronising fields between an Initiative and its Epics when the link is created, or…

Hello @Petr Sigaev If you don't mind using another solution, the add-on Elements Copy & Sync lets you do just that. I'm the Product Manager of the app, and when creating an issue from an Epic, you can just configure which users you want added to any custom user picker. It looks like this : With this simple configuration,…

Hello @Ted If you don't mind using a paid app, another solution would be to use Elements Copy & Sync. I'm the Product Manager of the add-on which lets you create as many issues as needed during a post-functions. The advantage is that you can copy information from the original issue to all the created issues if you need to,…

Hello @Tyler Stephens Another solution would be to use the add-on Elements Copy & Sync, which lets you copy all kinds of fields, including cascaded select lists. I'm the Product Manager of this add-on which is available on Jira Cloud and Server/Data Center, and I'll gladly answer any question you may have. Regards, Julien

Hi @Michael I believe our Marketplace add-on Elements Copy & Sync will let you do exactly this, quite easily. For your use case, I would advise using an operation which lets you create issues dynamically from an Epic, depending on the number of components in the Epic, and create Epic Links between each issue and the Epic.…

Hello, I'm the Product Manager for Elements Copy & Sync, which is an app developed by the same editor as Elements Connect. What you're trying to achieve is actually quite possible by using Connect and Copy & Sync together. As you will see in our documentation (section "Multiple issues" in…