Hi community,
I need a little bit help for an automation with asset and smart value. I think it's basic but I am new in automations with asset.
So I have an ObjectSchema called "Organisation" in this there is an ObjectType called "Fournisseurs" wich contains an Object called "Toto". The Toto attribute called "Courriel" is the email address of Toto
In my issue I have an asset customfield called "Fournisseur" that allow the assigne of the issue to select one object in the ObjectType "Fournisseurs".
I want to send an email of the Object selected in the field "Fournisseur" (Toto in this example).
I am facing two problems.
First the AQL request in lookupObject can't find the object :
And second problem if I replace "{{issue.Fournisseur}}" by "Toto" (the value in the customfield Fournisseur). The object is found but Automation failed to get the value of the attribute "Courriel".
Here is the log :
I use a lookup syntax found here : https://support.atlassian.com/cloud-automation/docs/jira-smart-values-insight/#SmartvaluesInsight-Lookupobjects
Bonus question : Is it possible to add issue attached filed in the mail send by automation ?
Sorry for this very long message and thank you for your help :)
Hi @Tom Lister ,
I tried it and it doesn't work.
The log say that it was impossible to send the mail because the "To" field was empty.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Mario GELES
Could you add some log actions to your workflow to see the direct output of the syntax?
There are some other examples here
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As you said I add some log actions and it seems that the lookupObjects doesn't work, there is no value
I forgot to mention that The objectType "Fournisseurs" is child of the ObjectType "Gestion" but when I create the customfield "Fournisseur" I didn't have to mention the parent ObjectType for my AQL to work.
Maybe in automation it's mandatory ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you @Tom Lister with the help of the audit log I was able to resolve each problem one by one.
So the good AQL was :
ObjectType=Fournisseurs AND Nom = "{{issue.customfield_10161.label}}"
And the proper way to call the attribute of my object was :
{{lookupObjects.Courriel}}
Everything is working fine now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.