Next-gen project automation assign an Epic

Jonathan_Kaczynski
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 15, 2019

In the automation section of a new next-gen project, I am trying to conditionally assign new tickets to a specific epic, but it is failng with the error "gh.epic.error.not.found".

When I configure the "Then" section of the automation, in specifying the target Epic Link, the text entry box turns my epic name into the issue id, DATA-1.

Comparing this to the "Add to Epic" flow which goes by the the issue name, not the issue id, I hypothesize that there's a potential bug in Automation configuration. If next-gen projects handle epic assignment purely by name, then the configuation text shouldn't have replace my desired epic/issue name with the related issue id.

 

1 answer

0 votes
Vasi
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 4, 2019

Hey Jonathan,

It's been quite some time, so I just wanted to check if you still experience this issue.

I was trying to configure something similar to what you are describing, however not entirely sure how you are configuring automation rule.

Could you please provide some screenshots and also specific conditions you were using?
I will try to reproduce it and file a bug if needed.

Cheers,
Vasily

Suggest an answer

Log in or Sign up to answer