scenario: we have two object types in schema 'Manufactures' and 'Type of devices'. In the third object type 'phones', there are various objects that are linked to objects of manufactures and type of devices. Now, using these asset objects through asset field in the portal forms, I am able to get two field Manufactures and Type of devices populated. In the third asset field 'Item' in forms , it should only display the object based on the selection of the above two field. the filter work item scope used is : "Manufracturer" = "{{issue.customfield_10231.label}}" AND "{{issue.customfield_10232.label}}" IN "Type Of Devices". But I am unable to populate the Item asset field.
I'm with @Marc -Devoteam-
Likely we need more details but based on assumptions these are few things to check:
1. The attribute has to be first and the value has to be at the end, so
"Manufracturer" = "{{issue.customfield_10231.label}}" AND "{{issue.customfield_10232.label}}" IN "Type Of Devices"
becomes
"Manufracturer" = "{{issue.customfield_10231.label}}" AND "Type Of Devices" IN {{issue.customfield_10232.label}}"
2. You are not using placeholders. This is necessary to use issue filter scope, so
"Manufracturer" = "{{issue.customfield_10231.label}}" AND "Type Of Devices" IN {{issue.customfield_10232.label}}"
becomes:
"Manufracturer" = ${issue.customfield_10231.label} AND "Type Of Devices" IN (${issue.customfield_10232.label})
3. You have to make sure the fields you are referencing are supported. They have to be certain system fields or asset fields only. If they are supported (asset fields), then you can change it so that
"Manufracturer" = ${issue.customfield_10231.label} AND "Type Of Devices" IN (${issue.customfield_10232.label})
becomes:
"Manufracturer" = ${issue.customfield_10231} AND "Type Of Devices" IN (${issue.customfield_10232})
Note too that if you did want to match by the label you have to add a part so that it matches for every single object and not just one, that is why matching by key is easiest. The asset field and the asset attributes in the backend are storing keys, so you don't need .label
4. Make sure everything is spelled correctly and it may be case sensitive. Is Manufacturer spelled the same way on the asset attribute? Is the T, O, and D all caps on the asset attribute?
5. You just need to list the customfield_id not issue.customfield_id
"Manufracturer" = ${issue.customfield_10231} AND "Type Of Devices" IN (${issue.customfield_10232})
becomes:
"Manufracturer" = ${customfield_10231} AND "Type Of Devices" IN (${customfield_10232})
Hope this gets you to a starting point:
"Manufracturer" = ${customfield_10231} AND "Type Of Devices" IN (${customfield_10232})
You can get more info here: https://support.atlassian.com/assets/docs/configure-the-assets-object-field/
I just realized the documentation says you have to use .id or .label. I've actually never used it. I've only used it once if I was matching by the label, but never for any attribute that wasn't set as the label. I haven't had any issues. :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the community.
Please provide more context on the configuration made in assets, provide screenshots with object details and attributes.
I'm confused as you seem to object type and schemas.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.