Automation - Assignee field populated from Asset object custom field

[Davide Cioranu]

Hi all,
I'm currently trying to setup an automation that allows me to populate the Assignee field with the entry in Asset object field.
I have 2 Asset object fields, one called Assigned agent and the other IT Team. This because I couldn't find a viable way to group agents via the group picker option.
As it currently stands, the two Asset object field look at the Assets  (Department and Employee) and they feed back to the custom fields. There is additional filtering which limits which users are being displayed in the Assigned agent depending on which IT team is selected.

I currently need an automation that populates the Assignee field with the Assigned Agent entry. 
Is there an option available to do this?

Many thanks
Davide

[Alex Koxaras _Relational_]

Hi @Davide Cioranu 

You could use Jira automation to populate the assignee field using smart values like {{issue.fields.Assigned agent}}. I would propose to use the log component to see if the proper value is returned from that smart value. Let me know if that works for you.

[Davide Cioranu]

Hi Alex, 
Thanks a lot for the reply. You mentioned the use of log component, is this a component that needs to be added to the project? Is there a guide on how to set this up?
I've tried to use the smart value you provided but the system threw back this error, which I've seen before
"Specified user does not exist or you do not have required permissions"
Are you able to redirect me to the log component setup?

[Davide Cioranu]

Hi Alex,
Just managed to setup the Log component.
I've tried what you advised and also I've tried {{issue.Assigned agent.name}}. Both of them are feeding what's in the screenshot.
Name Surname it's matching the agent name and also user in Jira(the one there is just a placeholder). 
Does the smart value need to match a specific criteria? 

[Davide Cioranu]

Hi Alex,
Just managed to setup the Log component.
I've tried what you advised and also I've tried {{issue.Assigned agent.name}}. Both of them are feeding what's in the screenshot.
Name Surname it's matching the agent name and also user in Jira(the one there is just a placeholder). 
Does the smart value need to match a specific criteria? 

[Alex Koxaras _Relational_]

@Davide Cioranu to assign issues you need to have the user ID. I'm not sure this will work with his/her name. Furthermore can you confirm that the actor of the automation rule has the assign issues permission?

[Davide Cioranu]

Hi Alex,
I've tried using the account id with the following values
{{Assigned agent.accountId}}

{{issue.Assigned agent.accountId}}

{{customfiield_xxxxx.accountId}}

but on the debug they all came blank.
Is there any permissions required for the actor to look at the values within the schemas in Assets?

Thanks

[Alex Koxaras _Relational_]

Can you please share a screenshot of the assignee agent on the assets, the rule, as well as the value of the field inside an issue? 

[Davide Cioranu]

Hi Alex.

Assigne agent in assets 

rule to gather the Asset from Assets

the rule

If I run this rule, this is what I get from the Output:

Assign issue

Debug message

Issue was already unassigned

It's almost like the value for the accountId cannot be found.
I've checked the permissions and I have it permissions to assign and browse.
I've also run the rule as myself as author and it didn't work.

[Davide Cioranu]

@Alex Koxaras _Relational_ 
Over the weekend I've tried investigating this further by looking more into the community, but due to it's specific nature I was not able to find anything similar, do you know if atlassian support can be contacted for this?
In the documentation I can see "accountId" being used, however when I use it is blank, and  if use ".id" or ".key" these work fine, so it's definitely not a permission problem.