global rule in the automation module does not work

[Eric Roetenberg]

Hello

I have created a global rule in the automation module.

When a user story is created it should look at the parent epic (this can be an Epic from another project) if the value of the field <<reporter>> is equal to XXXX

then set the value of the field yyyy within the user story to zzzz

But the rule does not work what am i doing wrong.

[Bill Sheboy]

Hi @Eric Roetenberg 

This could be a timing issue with the Issue Created trigger, where all of the data is not yet available at the moment the rule executes (e.g. the trigger issue's epic info).  Please try adding a Re-fectch action immediately after the trigger.  That will slow down the rule and re-load the data before trying the condition.

Kind regards,
Bill

[Trudy Claspill]

Hello @Eric Roetenberg 

Can you confirm that the issue in the Audit Log for the rule has a parent Epic where the reporter on that Epic matches the user you have specified in the rule?

Can you tell us whether the project specified for the issue in the Audit Log is a Team Managed project or a Company Managed project? It would say which it is at the bottom of the navigation pane on the left when you are viewing that project.

[Eric Roetenberg]

Hello @Trudy Claspill 

Hello

Yes the details are correct
and it is a company managed project

[Mark Segall]

Hi @Eric Roetenberg - When you click Validate Query on your condition, does it return any results?

[Eric Roetenberg]

Hello @Mark Segall Mark Segall

yes i become a result of 15 issue