Automated set assets to JIRA SW tickets after creation based on summary

[Peters Dominic]

Hi community,

i try the best to describe my case. I need to link an asset to a ticket after creation if there exists an entry for that. For example a ticket is created with a summary of "7 Zip" i want to link the Asset "7 Zip" to the issue.

I created an automation rule for this it says always success and the log action give me the correct values, but nothing happens^^.  Are they some other things to do for a software project? I need this for JIRA SW not JSM.

Maybe for better understanding of the situation: we have a software project with a public form who users with the link can request a "Tool"(its just software), i want to check is there already an entry for the requested "Tool" and link them int the issue or not then create a new asset with different fields as attributes.  

Here is my automation rule:

And an example view of the issue:

It looks like a bug for me that this doesn't work and there is NO error message in automation log but nothing happens on the ticket, its always says: "SUCCESS"

Im open up for anything

Thank you in advance

[Peters Dominic · Accepted solution]

Ok i could solve it by myself. I think the core problem was that i thought it is maximum difficult to build and tried to work with an AI assisstant.

I took a deep breath and let my own brain work!

My LookUpObjects was this: objectType = "Tools" AND Name = "{{issue.summary.trim}}"

The last part is not something you do with "LookUpObjects", it is the final value for the "edit work item" part in automation.

Also i deleted the JSON action, noticed from @Trudy Claspill thank you very much. So this my clear resolution: (The important parts)

and the Edit work item:

Thank you very much guys!

[Trudy Claspill]

Hello @Peters Dominic 

You must not specify the field you want to set in both the JSON and by selecting it from Choose fields. You need to specify it in only one or the other location.

If you want to set it by selecting the field from Choose fields then you can set the field value thus:

Name LIKE "{{lookupObjects.first.Name}}"

And delete all the JSON code in the More Options area.

[Peters Dominic]

Hi @Trudy Claspill yes thats true, i deleted the JSON in advanced section, i was frustrated ans ask ChatGPT for help and he says i need them both^^. 

I just select the field and added Name LIKE "{{lookupObjects.first.Name}}" but now i get an CMDB rech error message in log, i also noticed in my log action that the "ObjectID"  is always empty this looks not good.

The log action has the correct values (excep the ID) so the lookupobject is maybe not the problem?

Thank you very much for your help!

[Kai Krause]

Hi,

i think you can do the lookupObjects directly in the field,
and you can also put the query directly in the field. 



BR
Kai

[Trudy Claspill]

Hello @Kai Krause 

What you have proposed will not work.

The smart value {{lookupObjects} is valid only after the Lookup Objects action has been used.

https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-objects

[Trudy Claspill]

Or were you only trying to demonstrate an alternate smart value to use in the Edit action?

[Kai Krause]

Hi, yeah my bad. Its not clear enough . Sorry 

BR
Kai