When creating issue within the epic by automation rule reporter field not copy from the epic

[Vishnu Vardhan Chenna]

When creating issue within the epic by automation rule reporter field not copy from the epic but still it the reporter was Automation for Jira

[Walter Buggenhout · Accepted solution]

Hi @Vishnu Vardhan Chenna,

If the parent you are setting with this rule is correct, the copy the reporter from trigger issue instead of parent issue. 

Hope this helps! 

[Vishnu Vardhan Chenna]

Hi @Walter Buggenhout 

it's working fine

thanks alot!

[Bill Sheboy]

Hi @Vishnu Vardhan Chenna 

Adding to Walter's answer (and for your future reference in rule writing)...

Your create issue action is both setting the Parent (to an epic) and trying to use that parent's fields (e.g., Reporter) during the issue create.

I have seen this work inconsistently, unpredictably setting the field to the expected value, to the Automation for Jira user, or null.  My hypothesis is this is a timing (or field ordering) problem in code which passes the data to the issue create function, where if the Parent is not yet set there is uncertainty as to the source value.

And so the work-around for this non-deterministic behavior is to copy from the source issue when possible (as Walter suggested) or to create the issue first and then edit it afterwards.

Kind regards,
Bill