Assets as services & approvers

[Daniel Ziemniak]

Hey all,

So recently we switched to jirasm cloud with asset addon.

In our company, we have Access Management introduced. Users must ask for approve of tool owner in order to get access there.

We have a lot of services and we'd like to automate it.

Currently, schema looks like:

Services Catalog. Every asset there is a separate service with some attributes. The one that interests me is called "Owner".

What I would like to achieve?

When user goes to our service desk, it picks a service and access approver - owner - is assigned as "Approver" automatically.

I know I should use for each component in automation and lookup objects, but that's all I know. Could someone help me with that? I tried to look over documentation but somehow it's complicated, the way Atlassian describe it.

[Mauricio Heberle]

If understood it correctly, you are looking for something similar to this:

Lookup value: objecttype = "Employees" and "JIRA_USER" = {{reporter.accountId}}
Edit issue field:  "{{lookupObjects.Manager.JIRA_USER.accountId}}"

[Daniel Ziemniak]

Well kind of.

There's no need for two field value comparators.

Also, services have defined owners, so I think "JIRA_USER" = {{reporter.accountId}} is unnecessary.

The biggest problem here I see is with smart value - lets assume that there's a field called "Service Approver" in a scheme called Services. User picked a service called "Foo" from dropdown field linked to services list. Should it look like that?

{{lookupObjects.Services.(Service Approver)}}?