Can you filter an Asset field on select list custom field

[Jeremy Wood]

I have found lots of documentation around how to filter an object field based on another object. But can you filter an object based on a select list custom field? 

I would like to cerate a set of software assets and filter them based on the department that is selected. Department is already an existing field on our tickets. Rather then having to create a new asset for department, and go through the work of updating all existing request types to use the new object, as well as having to update historic tickets, i would ideally be able to filter off the drop down. Is this possible? 

[Trudy Claspill]

Hello @Jeremy Wood 

Can you provide a walk through of this use case?

So you have a Department field in your issue. It has value X. How would you use that procedurally (not the technical implementation) to get a subset of your Software assets?

How does that relate to the data that you have in your Software assets?

What attribute in your Software assets are you comparing to the Department field in your issue?

What values are in that asset attribute field for comparison to the Department value?

[Jeremy Wood]

Hi Trudy.

Ideally the software assets would have matching department Attribute. So when someone selects a department, it would filter to show only software that has a matching department field.

So, when creating a new request you would first pick the department, and then you would select the software you want. Ideally it would be used to filter the software list and make it quicker for teams to find the software they need. 

[Trudy Claspill]

Yes, you can do that by setting the context for the custom Asset Object field you create and add to your request screen. This document provides guidance on creating such fields.

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

What type of field have you created for the Department field for your request?

What type of Attribute have you created for Department for you object?

If the attribute and request field don't use the same data source then you run the risk of having a Department field value in your request that doesn't match to the Department values used in your objects. 

[Arkadiusz Wroblewski]

Hello @Jeremy Wood 

Yep this is possible, but only if the Department select list values match something in your Assets data.

You can use the Assets object field with Filter work scope (AQL) and reference the Jira custom field directly, for example with the custom field ID placeholder like:

Department = ${customfield_xxxxx.label}

I using something similar for my ERP System.

That said, the important part is that the value in the Jira select list and the value in the Assets attribute must match cleanly, otherwise the filter will not return anything.

https://support.atlassian.com/jira/kb/how-to-work-with-select-list-multiple-choices-custom-field-and-assets-custom-fields-to-retrieve-matching-objects/ 

Have a great start Weekend ☀️