Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Filtering the values in an Asset field based on another non-Asset custom select field

Zeeshan Khan
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 16, 2026

I have a custom field "Field A" that is a single user picker field and shows users filtered on Active Directory security groups. Field Id is customfield_10373. Screenshot below:

Field-A.PNG

 

Now I have created another Asset field called "Field B" in my People schema and referenced by "Employees" object and its fetching all the employee names etc. when used in a form. I want "Field B" to show filtered users like the ones shown in Field A and not all the employees when a user types in a user name in the field. How can I do that?

Tried doing this below but didn't work.

Field-B.PNG

2 answers

2 votes
Andrea Robbins
Community Champion
April 16, 2026

Hello,

Hate to be the bearer of bad news but this is not possible. Either turn the custom select field into another asset field or use a system field for this to work as described here:

https://support.atlassian.com/assets/docs/configure-the-assets-object-field/

Filter using another Assets object field

You can use the Filter work scope (AQL) field to reference another object field within the work item. This allows you to create a cascading list where the options in one list depend on the selection made in another.

...

Filter using a system field

You can use the Filter work scope (AQL) field to reference system fields from within a work item, such as Assignee and Project.

For example, to show a list of laptops owned by the current Assignee, configure the Filter work scope (AQL) field with:
objectType = “Laptop” AND "Owner" LIKE ${assignee.label}
In this case, each laptop object would have an "Owner" attribute that matches the assignee's name in Jira.

...

 

Jira system fields are case-sensitive and must be typed exactly as shown in the table below.

Work key

Label / Description

Multiple

Type

${key.id}

${key.label}

assignee

Assignee

false

ApplicationUser

userKey

Display Name

dueDate

Due Date

false

Date

dueDate

dueDate

fixVersions

Fix Versions

true

String/Custom Assets object

Id

Name

issueType

Work Type

false

String/Custom Assets object

Id

Name

components

Components

true

String/Custom Assets object

Id

Name

priority

Priority

false

String/Custom Assets object

Id

Name

project

Project

false

String/Custom Assets object

Id

Name

reporter

Reporter

false

ApplicationUser

userKey

Display Name

resolution

Resolution

false

String/Custom Assets object

Id

Name

summary

Summary

false

String

summary

summary

0 votes
Liz Tanner
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
April 16, 2026

Hey @Zeeshan Khan! I had to zoom way in to catch the error, but I think you're missing a second curly bracket. If you change ${customfield_10373.label)) to ${customfield_10373.label}) I think you'll be set!

Zeeshan Khan
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 16, 2026

Thanks @Liz Tanner , that doesn't work as well unfortunately. I have updated my Filter Scope (AQL) to the below and its giving me AQL Syntax Error.

objectType = "Employees" and object having inboundReferences(Name IN (${customfield_10373.label}))

 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
ENTERPRISE
TAGS
AUG Leaders

Atlassian Community Events