Filter an asset Custom Field with AQL in issue create screen

[reza rouhafza]

Hi there.

It’s a simple and common requirement, and I haven’t found a way to implement it in Jira.

I have an object type called “Employee” with approximately 2,000 objects.

I have an Asset custom field called “Employee_CF” that I want to populate in Jira Service Management (JSM) with multiple Employee objects. The problem: I want to query employees by various attributes to return a subset that fits the issue context. For example, I want to add employees who are female and part of Team A. There are several options in Jira:

• “Allow selecting all objects” isn’t suitable, because I don’t want all employees added to an issue.

• “Filter Issue Scope (AQL)” doesn’t suit my needs either: it effectively requires adding all Employee attributes as driver fields on the form. If any of them is left empty, the Asset field returns no results (placeholders don’t resolve when a driver field is empty).

Example
Object Type: Employee
Attributes: {gender, team, role, year of birth, technical expertise, status}

• I want to select all employees who were born in 1995.

• I want to select all employees in “Team A” who are male and currently active.

• I want to select Bill without specifying all of his other attributes.

Question: What is the recommended approach to achieve optional, attribute-based filtering for an Asset field in JSM?

[Jeroen Poismans]

Hi!

At this point this is not possible, however there is a setting on the Asset Field config that might come close:

This could work for a limited amount of attributes. You could add gender, email, team name ... here (if it is present as an attribute on the employee). The search will then take thes attributes into account.

Hope this helps!