Automation doesn't seem to recognize issues as EPICs in Team-Managed Projects

[Brenden Forte]

I've been writing automation to link epics together but it seems like ever since one of our team migrated to a team managed project, the issuetype="Epic" criteria is failing. How do I reference an "Epic" issue type in a team managed project? 

[Brenden Forte · Accepted solution]

Hi All,

I found a work around by using a JQL condition to query the correct issue types, but using the "Issue Fields Condition" >  Issue Type / Equals / Epic will consistently fail the rule. 

Looking in the audits, I can see that Epics from Team Managed Projects were triggering the rule as expected but would result in "No Action Performed" // Details: Issue did not match the condition.

As soon as I removed the issue fields condition component and switched to the JQL condition, it resolved everything. Very weird.

[Bill Sheboy]

Hey, Brenden.  Good catch!  If you are on a paid Jira instance you may want to submit that to support as a defect: https://support.atlassian.com/contact/#/

__Bill

[Kris G _Alacriz_]

Hi @Brenden Forte , 

Are you using JQL to check matching epics? If yes, try to run this JQL from advanced search area to see if it returns any result. Your criteria looks good for a team managed project.  

You must look in the audit log too to see if the automation rule has failed and why. I hope this helps. 

best,
Kris 

[Bill Sheboy]

Hi @Brenden Forte 

That is curious; I am able to reference epics as such for team-managed projects in automation rules.  Please consider posting an image of your automation rule and the audit log with the failure/symptom; that may provide more context for the community to offer ideas.  Thanks!

Best regards,
Bill