nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Filter Issue scope (AQL) for Assets using "Organizations"

Tobias Bosshard

I would like filter assets objects using the (locked) field "Organizations".
Example:
The reporter is part of a organization in the jira project (e.g. PowerWorker). The machines (objects in assets) have a field like "company".
Now, I would like filter the machines (from field "company" e.g. PowerWorker) using the (locked) field "Organizations" (customFieldId=10002). How should be the string for the Filter issue scope (AQL)?
Thanks a lot for any advise!
BR Toby

Accepted answers

Rodney Dsouza _Atlassian Certified Expert_

@Tobias Bosshard, @AV , @Dylan Robinson

Although this is possible on Jira Server/Data Center, it is NOT POSSIBLE on Cloud as of right now.

The fact that it has been possible on DC has created a few web pages on the internet giving us false hope/indication that it would work on Cloud.

Atlassian has said specifically said (on this page: https://support.atlassian.com/jira-service-management-cloud/docs/use-placeholders-to-replace-information-depending-on-context/ ) that

" Placeholders cannot be used in the Filter Scope (AQL) field in the Assets Objects Field Configuration screen."

However, that does NOT appear to be true _anymore_ since I have personally successfully used issueType as a placeholder in Filter Scope (AQL).

Looking at the documentation for Cloud, we see that some fields are supported on Cloud now, but unfortunately not Organizations.

https://support.atlassian.com/jira-service-management-cloud/docs/configure-the-assets-object-field/#Filter-using-object-fields-from-within-the-issue

Here are some Suggestions that you can upvote if you want this feature worked on (but I suggest you don't hold your breath)

https://jira.atlassian.com/browse/JSDCLOUD-10989

https://jira.atlassian.com/browse/JSDCLOUD-10185

https://jira.atlassian.com/browse/JSDCLOUD-12311

All comments

Tobias Bosshard

As it seems, there is currently no solution to this. Is that correct?

AV_0v37x5

I am actually trying this exact thing and found your post, so far I can't get it to work either.

I have an asset with a field called 'ShowForOrganisation'.
In there i Just type the Organisation's name which I want the field to be shown for.

Then in AQL i try to filter it:
ShowForOrganisation = "NAMEOFORGANISATION" > this works perfectly
however when I try the same trying to use the Organisations field:
ShowForOrganisation = ${customfield_10002} > this does not work

I tried fiddling a bit with customfield_10002.name or.label, but that doesn't seem to work.

So After this I found out the Organizations field can contain more then 1 value, which would mean the query should be like this:
ShowForOrganisation IN (${customfield_10002${0}})

Unfortunately I didn't get this to work either. I am currently still trying to achieve this.

Dylon Robinson

Attempting to use a similar function

Object attribute: Location

Filter scope: Location = ${customfield_10002}

Does not work

Filter scope: Location = "NAMEOFORGANIZATION"

Does work

We really need an option to dynamically filter based on this locked field.

Rodney Dsouza _Atlassian Certified Expert_

@Tobias Bosshard, @AV , @Dylan Robinson

Although this is possible on Jira Server/Data Center, it is NOT POSSIBLE on Cloud as of right now.

The fact that it has been possible on DC has created a few web pages on the internet giving us false hope/indication that it would work on Cloud.

Atlassian has said specifically said (on this page: https://support.atlassian.com/jira-service-management-cloud/docs/use-placeholders-to-replace-information-depending-on-context/ ) that

" Placeholders cannot be used in the Filter Scope (AQL) field in the Assets Objects Field Configuration screen."

However, that does NOT appear to be true _anymore_ since I have personally successfully used issueType as a placeholder in Filter Scope (AQL).

Looking at the documentation for Cloud, we see that some fields are supported on Cloud now, but unfortunately not Organizations.

https://support.atlassian.com/jira-service-management-cloud/docs/configure-the-assets-object-field/#Filter-using-object-fields-from-within-the-issue

Here are some Suggestions that you can upvote if you want this feature worked on (but I suggest you don't hold your breath)

https://jira.atlassian.com/browse/JSDCLOUD-10989

https://jira.atlassian.com/browse/JSDCLOUD-10185

https://jira.atlassian.com/browse/JSDCLOUD-12311

Tobias Bosshard

Dear Rodney,
thank you very much for your summary.
Yes, all we can do is vote and wait...
BR Toby

Amos_x3zpvn

I'm currently trying a very similar thing and it would appear that there is no way to dynamically look up custom fields (despite the example in https://community.atlassian.com/t5/Jira-Service-Management-articles/Announcing-Filter-Issue-Scope-for-Insight/ba-p/1737942).

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management