Using advanced field editing to inherit Team using automation

[Nate Ballantyne]

Hello, I'm trying to inherit the "Team" field from parent issues but I'm seeing an error (just says internal server error in the audit logs). Is someone able to point out what I'm doing wrong here?

Thanks in advance!

[Bill Sheboy · Accepted solution]

Hi @Nate Ballantyne 

Would you please post an image of the audit log details showing the rule execution?  That may help provide some context for this error.  Thanks!

And also...

The Issue Created trigger can fire so quickly some issue data may not be available when the rule starts.  This symptom can appear as failed steps, or unexpected behaviors, as the fields are null.  The work-around is to always add the Re-fetch Issue action immediately after the Issue Created trigger.  This will slow the rule down a bit, reloading the issue data before proceeding with the other steps.

Perhaps try adding that action to see if there is a problem with access to the parent issue's data.

Kind regards,
Bill

[Nate Ballantyne]

Hey @Bill Sheboy thanks for the message.

This is what I get in the audit logs:

I've also made the change as suggested (this is for my rule that does the change on transition):

[Bill Sheboy]

Thanks for that information.  I do not believe the Team field is fully supported that way for automation rules yet: https://jira.atlassian.com/browse/AUTO-525

There are a couple of things to try for a work-around, and let's try the simplest first, changing this "{{issue.parent.team}}" to "{{issue.parent.team.id}}"

That will use the internal id value for the team to try to set it.  (Without the .id it was returning the entire Team object, which will not work with the JSON in the format you show.)

[Nate Ballantyne]

That worked! Changing the value to what you suggested solved this, thanks for your help (again!)

Regards,
Nate

[Bill Sheboy]

Awesome; I am glad to learn that helped!