Automation of Epic, creation of tasks, then association of epic link to newly created tasks

[Patrick Hendry]

I am moving a service management ticket over to a software project. When moving the service management ticket, we are setting it to an epic in a software project. The jira automation I have in place is to:

When issue is moved from project A - B

AND issue type is Epic

Create A, B, C tasks

Then update A, B, and C epic link to the original epic that moved over.

I cannot figure this one out. What is also weird, I can create a sub-task that gets associated to the epic, but not a story, bug, or task. 

[Patrick Hendry · Accepted solution]

I've tried various way to get the child tickets that are created from the trigger to have the epic link to the trigger epic moving over from another project. Still no luck tying into that epic link for the child task. 

[Bill Sheboy]

Looking at the rule you have posted, are you trying to make the newly created Task a child issue of the trigger issue, epic?

If so, have you tried to set the epic link at the same time as the issue create?  Please show an image of that rule action.

[Patrick Hendry]

What's interesting, the sub-task type logic works fine, but I want to create tasks under the epic, not sub-tasks. Subtasks work, tasks fail. 

[Patrick Hendry]

Perhaps because I'm moving the ticket and not creating a new one, the logic is trying to find the epic link for the original ticket, which in this case it doesn't have one since it's a service desk ticket being moved over to a software project and converted into an epic.

[Bill Sheboy]

When setting the Epic Link in the issue create, you cannot copy from trigger issue because it is an epic (and has no parent epic).  My apologies if I was unclear!

Instead type in the smart value {{triggerIssue.key}} and it will appear below the field.  When it does, select it to use it.

[Patrick Hendry]

It does create a task, but the epic link never gets associated. 

[Patrick Hendry]

Trying that now... "Instead type in the smart value {{triggerIssue.key}} and it will appear below the field.  When it does, select it to use it."

[Patrick Hendry]

It worked!!!!!!!!

[Patrick Hendry]

One last question. 

Just to reiterate my logic:

When ticket is moved from one project to another ->

When issueType = Epic ->

Create task with Epic link set to {{triggerIssue.key}} ->

Create 2nd task with Epic link set to {{triggerIssue.key}} ->

Then for the current issue (2nd issue created) create a sub task for that issue. 

The subtasks are being assigned to the epic, not the second child task created. Thoughts?

[Bill Sheboy]

At that point in the rule, "current issue" or {{issue}}, refers to the trigger issue still.

If you want to add subtasks to that second, created task, please change your branch to Most recently created issue.

[Bill Sheboy]

Hi @Patrick Hendry -- Welcome  to the Atlassian Community!

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected.  Those will provide context for the community to offer ideas.  Thanks!

Kind regards,
Bill

[Patrick Hendry]

Here is the audit: ACTION DETAILS: ["10139"]

ISSUE CONDITION The following issues passed: FUL-309

CREATE ISSUE Issues created successfully FUL-310

EDIT ISSUE Error editing issues FUL-309 (Could not find issue by id or key. (parent))

CREATE ISSUE Unknown fields set during create, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored - Epic Name (customfield_10011) Issues created successfully FUL-311

EDIT ISSUE Error editing issues FUL-309 (Could not find issue by id or key. (parent))

CREATE ISSUE Issues created successfully FUL-312