Cloning an epic and child stories from a company bases project to a team one

[Mariam Omran]

@Mark Segall , kindly need your help with my case. I have created an epic with it's child stories in a team managed project. then i moved it to a company one. now I want to clone it back to another team project and I created an automated rule for that. screenshots to follow. however when I open the epic card and go to the automation to run the rule i don't find it at all as if it doesn't exist. can you pls advice?

[Mark Segall]

Hi @Mariam Omran 

Thank you for starting the new question and sharing your screenshots.  Am I correct that you can actually see the rule in your actions menu and that once you select it, nothing happens?

Please provide this:

• Project Name(s) of Epic(s) you are trying to execute against
• screenshot of your Rule Details

If you have a rule set to execute manually and you've selected that rule from your actions, you should at least see something show up in the audit log so this is definitely a peculiar scenario. 

[Mariam Omran]

Hello @Mark Segall ,

Nope I cannot see the rule in the action menu of the epic at all.. It doesn't come up ! 

I did choose that the rule to be executed manually but it doesn't show up.. another 

so Here is a screenshot of the epic :

the rule shown in this pic is not the one I want to run 

The Rule details screenshots:

[Mark Segall]

Am I correct in my understanding that you created this on one project and now want to execute it on another?  Under the Rule Details there's an area for Scope which determines what projects this rule will be available to.  It is likely that because you created it on the original project, it is only available to that project.  You would then have two options:

1. Elevate the rule to a multi-project scope: You must be a Jira Admin for this, but you would go to Settings >> System >> Global Automation.  From there you can change the rule scope to multi-scope and add any additional projects where you want this rule to be an available action
2. Create this rule again on the new project.

[Mariam Omran]

Hello Mark,

I tried this again and still did not work !

[Mark Segall]

Let me take a step back on this.  Can you please confirm the following

1. The Problem: Your rule (Clone Epic 2) does NOT appear under the ACTIONS menu on the desired issue
2. Troubleshooting: You have verified that the rule scope (located in the Rule Details section) includes the desired project(s) you would like to have access to this rule.

[Francis Batilo]

HI @Mariam Omran

I'll try to assist you with your inquiry. You mentioned that you ran the automation rule and you weren't able to find the epic. Would you be able provide us some screenshot of the audit logs?

Also, if you can change your smart value to {{createdIssue.key}} instead of {{varNewEpic}} that might help.

Let me know how you go.

Cheers,

Francis

[Mariam Omran]

Hello @Francis Batilo Thank you for your support. 

For some reason this is all I am getting from the audit log ! 

NO actual log is showing up !

[Francis Batilo]

That's a bit peculiar, do you mind running another automation run until it becomes available on your audit log and show us the details of it?

[Mariam Omran]

I keep enabling it and disconnecting it and I get the same audit log. maybe that's why it is not showen.. shall I create this automation rule somewhere else other than the Company based project settings? 

[Francis Batilo]

@Mariam Omran

That might be a good idea and if you can run it on a different project under your sandbox. From what I can see, the rule has not been triggered despite it being a manually triggered automation, which is a bit weird. I'm expecting an error message of some sort to diagnose what the error is, but that's only when the rule is executed completely. 

Let me know how you go.

[Mariam Omran]

I have moved to another project but it is not working ! 

[Francis Batilo]

@Mariam Omran

I find this issue really peculiar. I expect at least an audit log from each trigger of the automation rule.

Anyway, if you're able to do this for me to see what's going on around the automation rules in the same project.

So, my intention is to see if a normal rule, without complexity, will run without a problem. To test this, can you create another manually triggered rule that just comments something into an issue. Maybe "Test Comment". Then, run the automation rule into any of your issues, maybe the one you want to clone later. 

If this manual automation rule works, then you can transfer the rules you have from the other to this new one. If it doesn't, you might need someone from Atlassian support to check out what is happening with your automation.

Let me know how you go.

[Mariam Omran]

I know !

Now I have done something different

I have created a whole new rule a blank one and started manually to create the conditions in it following cloning an epic one.

I started the 1st condition with an automatic tigger once issue is created and issue type is equal to epic. 

and saved it and ran it. 

and this is log ! 

I then changed the trigger to be manually and now I am back to square zero and shown in the log above !

[Francis Batilo]

@Mariam Omran

At least we can rule out that the issue occurs when the rule is a manual trigger.

Unfortunately, I'm not sure how to fix that and I think it would be best to contact Atlassian Directly. 

In the meantime, you can clone your epic by tweaking your rule to run automatically. Maybe use a new field or an existing field that you can play around with to trigger the clone. 

In terms of your automation rule, I think you might need to update the branching to be stories instead of For Parent (see my screenshot below).

[Mariam Omran]

Thank you @Francis Batilo 

it is still not working with me ! I have no idea why.. hence I might open a ticket with Atlassian ! 

[Luka Hummel - codefortynine]

Hi @Mariam Omran

I'm Luka from codefortynine and I think our Deep Clone for Jira app can help you clone your issues from company-managed projects to team-managed projects and back from team-managed projects to company-managed projects.

With our Epic/Tree Clone feature, you can easily clone whole issue hierarchies (Initiative ⇒ Epic ⇒ Story/Task ⇒ Subtask) from one project to another.

1. Navigate to the issue you want to clone

2. Click Action menu ••• > Deep Clone

3. Select Epic/Tree Clone

4. Configure and create your Epic/Tree Clone

[Mariam Omran]

Thank you Luka,

This is a very helpful tool. but I don't have the capacity to install and pay for it now. 

I am looking for the built in Automation in JIRA for now !

[Luka Hummel - codefortynine]

Understandable. If you still want to give the app a try, you can test the Deep Clone for 30 days, and the app is free for Jira instances with up to 10 users.

[Mariam Omran]

[Mariam Omran]

@Mark Segall  screenshots