Automation - Create Recurring Epics

[Tom Stevenson]

Hi all,

Does anyone know if you can create recurring Epics using Global automation that also consist of tasks? 

I can create the epic fine but how would I add the tasks inside of there?

[John Funk · Accepted solution]

Hi Tom - Welcome to the Atlassian Community!

You would actually want to Clone the Epic and all of its children. The Marketplace app Deep Clone is probably the best thing to use. 

[Tom Stevenson]

Thanks for the speedy reply John!

Are you saying there's no way to achieve this with just the built-in global automation section? I'm halfway there with the Epic being created I just need it to create some tasks for me inside of that Epic too.

FYI this is for recurring tasks such as sysadmin checks, I'd rather not have to clone anything and just schedule the Jiras to create themselves on a schedule.

Here's what I have so far:

[John Funk]

Sure you can do that. I would add a custom field or some value to the Epic when you create it. 

Then I would create a second rule that when an Issue Created and Condition for issue type = Epic then add a new action for Create issue for each child issue to create. 

In the child creates be sure to include the Epic Link field and use this code:

{{triggerIssue.key}}

[Tom Stevenson]

Sorry I'm new to Jira.

I've added a new label to the Epic which will hopefully qualify as the "custom field or value" you mentioned?

Does there need to be a second rule or can I just add the tasks as a component?

I am not following how to edit the Epic link field:

[John Funk]

Hey Tom - Sorry, I forgot that you are creating the Epic using the Scheduled Trigger. Yes, you can simply add a Branch as my buddy @Bill Sheboy  mentions above. 

The model I was using is when a Form is submitted in a JSM project and it creates the Epic automatically. Then I have various rules running that will create lots of child tickets based on values in the Epic. 

[John Funk]

Click on add Component and select Branch

Then Basic branch

Then Most Recently Created Issue

[Tom Stevenson]

Thanks John that sounds like it might be getting closer. It still seems to just create the Epic and no issues though - do you know where the problem is?

[John Funk]

Can you post the Audit Log for the results after you run it? 

[Tom Stevenson]

Here is the result, sounds like it's struggling to recognise the Epic creation?

[Bill Sheboy]

Tom, would you please post an image of the details section for your rule?  That may reveal a scoping issue which could cause this symptom.

If that does not help, it is possible the rule has become "glitched" due to several edit/publish cycles.  I do not know why that happens...just that it does.  The way to check for that is to disable this rule, and recreate it from scratch as a new rule.

[Tom Stevenson]

Hi Bill,

Sure I appreciate the help!

FYI I have successfully created the Epic AND the Tasks however it does NOT link them together, they are all created separately. It seems like the "Most recently created issue" logic doesn't function how we want it - I guess the Epic we're making doesn't quality as an "Issue"?

 

[Bill Sheboy]

Sounds like some progress!

Now inside the branch when you create the tasks, what value are you putting/selecting for the Epic Link?  You can try typing in {{issue.key}} as that will refer to the branched-to issue: the epic just created.

[Tom Stevenson]

Hi Bill,

I've tried most of the options in the branch behaviour but they either don't work with the previously posted error, or they just create the tasks and the epic separately and unlinked.

[Bill Sheboy]

Your earlier rule seems like it should work, with branch to most recently created issue, followed by creating the tasks and linking to current issue.  (I think I gave bad information earlier on what to use, which I will correct in the earlier post.)  How about this one:

• trigger: scheduled
• action: create issue (for your epic)
• branch: most recently created issue
  • action: create issue (for your task, and...)
    • For the Epic Link, type/copy in {{issue.key}}
    • This will appear below the field, and then you may select it for use
    • Inside of the branch, {{issue.key}} refers to the branch issue: your epic.
  • ...

[Tom Stevenson]

Hi Bill,

Thanks for your patience and support - we have success!

[John Funk]

Great! Can you post the final solution so future readers can see the implementation? 

[Tom Stevenson]

Sure! For the next poor soul who attempts this here is my final config. The key to the solution is the custom field inside the tasks linking it back to the Epic.

[John Funk]

Thanks for sharing!

[Bill Sheboy]

Hi @Tom Stevenson 

I believe you can create the epic in the rule, and then either...

• branch to most recently created issue, add the tasks in the branch and link to {{issue.key}} as that would be the epic, or...
• create the epic in the rule, and save its key with {{createdIssue.key}} in a variable, and then reference that for the linking of the tasks

Kind regards,
Bill

[Tom Stevenson]

Hi BIll,

For option 1 I don't see how to branch to the most recently created issue?

[Bill Sheboy]

Tom, it looks like you figured out the branch in the thread started by John.  Let's stick with that one to try to diagnose this.  Thanks!