nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Assets Automation

Nate Dickinson

I'm evaluating JSM premium because of the use of the assets application. I need to do the following, and am wondering if I need to involve automation to complete the task.

Given:

In assets

I have an object with the following attributes:

Name

component reference

In JSM

Asset Custom field-Client information

Filter scope is my Assets Object type-"clients"

In Automation: A client creates a JSM ticket and is assigned a component value given their existing customer information

Ask/Pseudocode:

I want JSM to automatically pull the object into JSM where component in jsm matches the attribute component reference in Assets.

I can currently manually search for objects within JSM, but I'm not seeing the action for this in the custom field, or JSM. I'm assuming this has to be done in automation. Is that correct?

Accepted answers

Mikael Sandberg

Correct, you have to do it using automation. Here is an example where the linked assets is populated with the reporter's assets when a request is created.

Screenshot 2023-02-20 at 11.07.31 AM.png

All comments

Mikael Sandberg

Correct, you have to do it using automation. Here is an example where the linked assets is populated with the reporter's assets when a request is created.

Screenshot 2023-02-20 at 11.07.31 AM.png

Nate Dickinson

Thank you Michael, If I'm just querying via components does this make sense?

"Name" = "{{components}}"

Name is the attribute in assets.

Nate Dickinson

This works but it's hardcoding the reference:

"Name" = clientname

None of these work though. Am I supposed to use a smart value? What documentation are you referencing for this?

"Name" = "{{Components}}"

"Name" = "{{issue.Components}}"

"Name" = "{Components}"

"Name" = Components

I keep getting this error:

No objects were returned from query.

No fields or field values to edit for issues (could be due to some field values not existing in a given project):

Mikael Sandberg

Use "Name" = {{issue.components.name}} instead, otherwise components would come back with the internal number instead of the display name. And to cover the situation where you have multiple components on the request you should use this one instead:

"Name" in ({{issue.components.name}})

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management