How to copy details from Epic link to SCHEDULED automation ticket?

[Carina Lora]

I've been trying to create a scheduled recurring action to do the following:

1. At scheduled day/time
2. Create a subtask within an existing epic
3. Subtask copies Assignee, Description, and Reporter from the linked epic
4. Send an email to the task reporter notifying them of the task created

A few different configurations have been tested, introducing steps to create a new issue, refresh issue data, etc. I suspect my issue is related to the required JQL query associated with the scheduling trigger. Currently, the JQL is issuekey=[destination epic]

So far, I've achieved:

• Issue is created on schedule
• New issue is a child of the parent epic

Missing:

• Copied description, assignee, reporter from the parent epic.

Could someone help me understand what I'm missing here? Thank you!

[Bill Sheboy · Accepted solution]

Hi @Carina Lora -- Welcome to the Atlassian Community!

I am a bit confused by your use case, as your description seems different from your example rule.  It seems like you want to:

• once a month, create a user story;
• linked to a specific epic;
• copy the following fields to the story from the epic: description, assignee, reporter; and
• send an email to the reporter to notify them.

Is this correct?  If so, your rule could be:

• trigger: scheduled monthly, with JQL of key = myEpicKey and with the option disabled to only run the rule if the epic has changed since the last execution
• action: create issue
  • issueType is story
  • set the Description, Assignee, and Reporter using "Copy from Trigger Issue"
  • set the epic link to {{triggerIssue.key}}
• action: send an email to {{reporter}} to notify them

This will work for a company-managed project.  If you are instead using a team-managed project then epic/story are linked using "parent" instead of "epic link".

Kind regards,
Bill

[Carina Lora]

Hi Bill! Thank you so much for the prompt and helpful reply. I was missing the checked box in the trigger JQL and had a refresh step in place instead. Digging through support answers got me somewhere, just not quite where I needed to go.

Your suggestion worked exactly as needed. Thanks again!