Update User in Asset object via Jira Automation using Lookup objects

[Tania Schmittou]

Jira automation to update User in Asset object to a new value using the Lookup objects action is giving a warning.  I know the Branch on AQL is removed from Jira automation as an option and documentation states to utilize the Lookup objects action instead. 

I am using an issue to manually trigger my test automation.  The automation is also updating the issue Summary to append lookupObjects.User.displayName which is recognized and can be addressed fine in the Edit Issue action.

For the Edit Object, I get a warning and it won't save.  Here is the flow snippet and the warning.  I cannot create a variable to use in the beginning of my automation because I don't have the value until after the lookup, so stumped on how to resolve this.  Any help is appreciated!

[Christopher Yen · Accepted solution]

Hi @Tania Schmittou 

We are still using Branch on AQL, but it just has to be a global automation. Is this going away?

I'm not 100% on this because my asset automations are just done through trial and error, but if running a rule against an issue in my instances I've had to add a asset field to run the edit asset action against. Are you able to use your lookup to link the objects to a field and then use the edit assets field attributes action to update? 

[Tania Schmittou]

@Christopher Yen -  Yes, I see the Branch for AQL is still available in global automation creation, but not otherwise.  Not sure where I read it was going away.  

Thanks for the information about Edit Object needing an asset data type defined custom field to perhaps work.  I will try that.  It was slightly confusing because my Create Object test worked.  

Thanks again!