Copy Assets object attribute to issue custom field via automation

[Carlos Chang]

Hi guys,

I'm trying to fetch object attribute and copy to custom field in the same issue, I'd like to use automation, is it possible?

There's a post-function that could perfectly get it done, unfortunately, this method only exist in Server/DC.

I know it's probably easier with groovy scripts, but it will not fulfill customer's expectations for now.

Kind regards,

Carlos

[Gideon Nolte _Jodocus_ · Accepted solution]

Hi @Carlos Chang

this can be done with Automation for Jira with the "Edit Issue" action and SmartValues

If the Object is present in a customfield of the issue, you can use the SmartValue {{issue.customfield_XXXXX.objectAttribute}} (e.g. {{issue.customfield_10500.Name}}). If the object is not present on the issue, you can use the "Lookup Object" action to get all objects specified by AQL. To access these objects' attributes, you can than use {{lookupIssues.objectAttribute}}.

Hope this helps. Feel free to let me know if you have any more questions

Greetings
Gideon

[Carlos Chang]

Hi @Gideon Nolte _Jodocus_ 

SmartValue works! Genius.

Kind regards,

Carlos

[jun lee]

Hi @Carlos Chang 

I am trying to copy object's attribute (manager) to a custom field (User Picker (multiple users)). Manager attributes have plural individual account. 

I added an automation rule, but it doesn't work. Can you help me?

[Gideon Nolte _Jodocus_]

Hi @jun lee ,

two things you would need to fix here: 

1. Use the "normal" way (not the Additional fields option) to set the field value. It's the field which with the placeholder "Type to find matching users". In there you should be able to set the value via a Smart Value.

2. Given that customfield_13809 holds an object of type "supportgroup", you will have to provide the "ENM_USER_MULTI" field with a list of account IDs rather than objects. What I mean by this is, that the current Smart Value `{{issue.customfield_13809.manager}}` will evaluate to the manager object(s) rather than the mangers' accounts which will most likely be stored in an attribute of type "User" on the "Manager" objects. Let's assume that the attribute which holds the manager's user  is called "Account". Then the correct Smart Value would be `{{issue.customfield_13809.manager.Account}}`.

Hope this helps. Let me know if you have any more problems with that.

Greetings
Gideon

[jun lee]

Hi @Gideon Nolte _Jodocus_ 

I tried second method like 

{{issue.customfield_13809.manager.Account}}

{{issue.customfield_13809.manager.Name}}

{{issue.customfield_13809.manager.email}}

However, Audit log is success althought it doesn't work

[Gideon Nolte _Jodocus_]

Hi @jun lee ,

could you provide me a screenshot of the attributes for the manager object type. Is the "email" attribute of type User? Is there an attribute on the Manger Object Type that is of type User? If yes, try using that.

Greetings
Gideon

[jun lee]

Hi @Gideon Nolte _Jodocus_ 

Yes, email is the attribute of the Manager object. 

I am trying with different field.  I added "department" attribute to the "manager" object, made a custom filed 13901 (object type), and I added automation rule as {{issue.customfield_13901.department}}

However audit log of the automation rule was failed.

ENMCOMM-379 issue has custom field 13901 ("ENM_manager") and custom field "ENM_Department"