How to filter issue scope (AQL) based on the object selected?

Yousif Al Rawahi May 21, 2024

In Assets, I have an object type called 'AVU', where there are information about each employee. Inside AVU object type there is attribute called manager which is linked to AVU object type.

I have created two assets field, one is for AVU, where you get the list of all employees, and another assets field is called manager, this will show his/her manager based on the AVU selected employee. So, when I choose any employee, the second assets field should appear his/her manager.

For AVU assets field, I have written objecttype="AVU" in filter scope (AQL), and in manager assets field I have written "manager"= ${customfield_11468.label} in filter scope (AQL). The 'customfield_11468' is from AVU field.

But it doesn't show the manager of the employee in manager field, it's empty. Is there a mistake in filter scope (AQL)?

1 answer

0 votes
Kris Dewachter
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 21, 2024

Hi @Yousif Al Rawahi ,

Can you share screenshots of the specific configuration of the 2 asset fields ?

Is the "Manager" attribute a reference to an AVU object? If so, you should be able to reference it like this :

manager= ${customfield_11468} 

Best regards,

Kris

Yousif Al Rawahi May 21, 2024

This is for AVU, list of all employees:

AVU.png

And this is for managers:

Screenshot 2024-05-22 084613.png

 

Is the "Manager" attribute a reference to an AVU object? Yes, it is.

Yousif Al Rawahi May 21, 2024

I'm getting the opposite using this configuration: manager= ${customfield_11468}

When I select the manager in 'AVU' field, it gives me its employee in 'manager' field. 

Kris Dewachter
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 22, 2024

Hi @Yousif Al Rawahi ,

So if I understand correctly, the first custom field gives you a list of all employees. Let's say I select employee "Yousif".

In the second custom field, this also gives you a list of all employees, but in the "Filter Issue Scope" you say : "Give me all employees where manager = Yousif".

So that's would explain why you see the opposite result you mention.

May I ask why you want the name of the manager in a separate custom field ? Basically, since you can ever only select one value, it seems to be for informational purposes only?

In the configuration of your first custom field, you could also add the "Manager" attribute in the "User Interaction"

Screenshot 2024-05-22 at 19.34.35.png

 

Like this, the name of the manager is displayed below the name of the employee in the dropdown selection.

 

Screenshot 2024-05-22 at 19.35.43.png

 

Best regards,

Kris

 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events