Set assignee by rule

[Antonia]

Hello,
I am trying to create a rule that creates a ticket for an asset on a specific date and automatically adds the assignee and request participants to the ticket.
So I have an attribute in my asset with a date. If the date is 3 weeks in the future, a ticket must be created. This works so far, but I can't get the assignee and request participants to be set automatically.

The field in which the persons are listed is called “Key Owner.” The first person listed in this field should always be entered as the assignee, and the rest as request participants. However, this does not work with the following values:

• {{object."Key-Owner"}}
• {{object."Key-Owner".Mail}}
• {{issue.Asset-Key-Owner.get(1).accountid}}
• {{object."Key-Owner".get(0).accountId}}
• {{object."Key-Owner".accountId}}

The field where the people are listed is an object field containing the users imported from Intune.

[Marc - Devoteam]

Hi @Antonia 

Is the "Key Owner" field an asset attribute or a custom field of type assets?

What does a log action give you as information, so add log action for the smart values:

{{issue.Asset-Key-Owner.get(1).accountid}} - seems wrong, as this implies Asset-Key-Owner is a user picker field on the issue.Any smart values starting with issue implies a field on the issue
{{object."Key-Owner".get(0).accountId}}
{{object."Key-Owner".accountId}}

Also loo at this community article and KB article.

• https://community.atlassian.com/forums/Jira-questions/Automation-to-pull-members-of-an-Assets-Object-Attribute-and-e/qaq-p/2309092 
• https://support.atlassian.com/jira/kb/add-users-from-asset-attribute-as-request-participants/ 

[Antonia]

Hi @Marc - Devoteam

Log action (it says nothing, but under create work item it says inactive user!?):

Is the "Key Owner" field an asset attribute or a custom field of type assets?

Unfortunately, I'm not quite sure what you mean, but maybe this screenshot will help:

[Marc - Devoteam]

Hi @Antonia 

See the community post and article I added.

This article provides information as wel,, https://support.atlassian.com/jira/kb/how-to-auto-populate-approvers-from-asset-objects-attributes-using-automation-in-assets/ 

Also make sure the user executing this needs to have the correct permissions.

Browse Users and Groups global permission, this is a global permission in Jira, needs tp be granted to the rule actor.

[Mikael Sandberg]

In your person object, do you have a reference to the user's Atlassian account? You can do that by having an attribute that is of the user type.

[Antonia]

We have a reference to the other object type, and it contains the user ID or email address, for example. Isn't that what I need? Because emails are also sent out and that works, but the assignee/request participant doesn't work.

Does it have to be a user attribute, or would an object attribute work as well?