Error: Epic not assigning in Automation from Trigger Issue

[Mary Prather]

Hi there, 

I have run into an error code for assigning the trigger issue to a new task in automation, the automation runs fine but I get the error below regarding the epic. I am wondering if anyone has ran into this issue before and knows how to fix it. 

Thanks so much

[Bill Sheboy · Accepted solution]

Hi @Mary Prather 

Are you using a company-managed or team-managed project?

Team-managed projects do not use the "Epic Name" field; they use "parent" to set the epic link for child issues.

And company-managed projects have "Epic Link" and "Epic Name", but both of those fields are being sunset.  You can use "parent" instead for that project type also.

Kind regards,
Bill

[Mary Prather]

Hi Bill, 

Thank you again for your help! It is a Team Managed project but when looking I do not have the option to select Parent, only Epic name and Epic Link 

[Trudy Claspill]

In Automation Rules for Team Managed projects, Parent is not yet a field that is available to select from the "Choose fields to set" list.

You have to use the More Options

In the "More options" => "Additional fields", paste the following within the created ticket

{
  "fields": {
    "parent": {"key": "{{triggerIssue.key}}"}
  }
}

[Mary Prather]

Hi there Trudy!

Thanks for your reply.  I made this change and it didn't work unfortunately. The error is shown below. 

[Trudy Claspill]

Can you show us the entire rule, please?

And what is the type of the Issue that is triggering the Rule?

[Mary Prather]

Hi there, 

Here is the entire rule. The issue type is a task 

[Trudy Claspill]

Using the "triggerIssue" smart value in creation of the Task (within the rule) to try to set the parent Epic for the new Task works only if it was an Epic issue that triggered the rule. You can only make an Epic the parent of a standard issue type such as a Task. You can't make a standard issue type a parent of another standard issue type. 

That is what the message is indicating. If a Task triggered the rule, then a Task is at the wrong level to be made the parent of the new Task you are trying to create.

Is the Task that triggers the rule a child of an Epic? Are you actually wanting to make the newly created Task a child of the same Epic as the Task that triggered the rule?

[Mary Prather]

Thank you for your help!

Yes the task that triggers the rule is a child of the epic I want copied, I want the newly created task to fall under the same parent epic. For context, each "epic" is a different client. When we close this specific task out we want it to re-assign and re-assign to the appropriate "epic" since it is a working task that needs to be completed frequently. Here is what it looks like on the list view. The issue we are trying to reassign is "Test Execution"

[Trudy Claspill]

This is the code that you need in More Options then

{
  "fields": {
    "parent": {"key": "{{triggerIssue.parent}}"}
  }
}

[Mary Prather]

IT WORKED!! Thank you so much for your help!

[Jack Brickey]

Hi @Mary Prather ,

In your screenshot I see copy labels for trigger issue twice. I would first remove one of those and observe the results. If it continues to fail, just for test purposes remove the second labels from the fields to be set. Let me know your results.

[Mary Prather]

Hi Jack!

Thank you for your help! I removed one of the label rules and still got an error, and then the second and still got the error as well. Please see the error log below :)

[Jack Brickey]

Thanks Mary, this is what I expected but wanted to prove. There are actually two errors in your initial Image. I am thinking along the same lines as what Bill posted above. Could it be that you are in a team managed project? If so use"Parent" is Bill indicated.