nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Accepted answers

Bill Sheboy

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

All comments

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

Bill Sheboy

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

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.

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 P 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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud