Custom Asset Object field in Issue populated via Automation Issue

[Brandon Edwards]

I have an Onboarding Request Type with a Jira Form. In the form I have a field that based on its value (Yes or No), shows one section or another. In one section is field in the form linked with a custom field in the issue. The custom field in the issue is tied to Assets > Object Type > Specific column. This works great in the form and even if I edit the field in the issue, the correct Object values show in the dropdown. 

The issue lies when the user in the form selects Yes (Selection of "No" shows them the Asset Object choices), then they are prompted to enter an address manually in 4 separate fields. Since the condition is setup to not then show the Asset Object field in the form, when the form is submitted, it comes in as blank. 

I have an automation setup where other fields in the form are edited upon issue creation, so I added logic to if the response in the form was "Yes" (This form field is also linked to a custom field in the issue type and I have added log actions in the automation to confirm the correct value is being seen), then Lookup Objects to grab the values tied to the specific value in Assets that I want (Also verified that they are correctly pulled with log actions), then put the value in the specific field. 

I am returning Successful runs in the automation audit log, but the field is not populating. The log shows that the field was successfully edited and log actions in the automation show that before and after the edit function in the automation, that the correct id, key, and name of the asset object match what should have been leveraged in the edit. 

In the edit work item, I have tried:

{{lookupObjects.first.key}}, {{lookupObjects.first.id}}

I then removed the smart value and tried the JSON approach with (field only allows a single value):

{
"fields": {
"customfield_10466": [
{
"key": "{{lookupObjects.first.key}}"
}
]
}
}

I have tried many variations. I originally had the custom field only slated for View in the Screens for the issue type. I have since added them to Create and Edit to ensure that is not causing an issue.

Any ideas?

[Trudy Claspill]

Hello @Brandon Edwards 

Welcome to the Atlassian community.

To enable us to help you, can you please provide screen images of the following:

1. Your entire automation rule.
2. The details of any step where you are using smart values
3. The details of the rule execution audit log entry for an execution that matches the steps shown in the image of your rule.

Besides that, in your Edit action are you calling out the Asset Object custom field only in the JSON, or have you left it selected also in the Choose fields to set list?

[Brandon Edwards]

Thanks Trudy for responding. I was able to figure it out after several more hours of trial and error. I was trying to use these two options (with id and key switched out as id was throwing field errors):

{
"fields": {
"customfield_10466": [
{ "key": "{{lookupObjects.first.key}}" }
]
}
}

{
"update": {
"customfield_10466": [
{
"set": [
{ "id": {{lookupObjects.first.id.asJsonString}} }
]
}
]
}
}

This kept saying it would be successful but the issue field was always blank. All of my log actions against the lookupObject would return the values that I needed, but Edit Work Item function would not write to it. Finally I found some documentation deep down that mentioned hardcoding your Workspace ID for Assets into the JSON. My final JSON was:

{
"update": {
"customfield_10466": [
{
"set": [
{
"workspaceId": "<My Assets Workspace GUID>",
"id": "<My Assets Workspace GUID>:{{lookupObjects.first.id}}",
"objectId": "{{lookupObjects.first.id}}"
}
]
}
]
}
}

This ended up working immediately and now it is writing

[Trudy Claspill]

I'm glad you found a solution!

Can you share the link to the documentation that mentioned using the workspace ID?

[Brandon Edwards]

Format the payload to update Assets Custom Fields via REST API | Jira and Jira Service Management | Atlassian Support