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 Scope on Insight/Assets custom field not working as expected with multi-select configured

Durell Demartini

Hello,

We have two custom fields of type "Insight object" (I understand it is called Assets in newer versions), used on a single request type form in Jira Service Management. They are both configured as multi-select: "Entity" and "Product."

Using the Filter Scope in the Products field configuration, we have configured Product to show only options that are based on the previous selection of Entity. This works as expected for single selection:

"Entity" = ${customfield_12345.label}

However, because both fields are configured as multi-select, as soon as we select multiple options in the Entity field, we see that no products appear.

Is it not possible to use multi-select in this manner or do we need to update the Filter Scope in the Products field configuration to something else to be able to show all products related to all entities select?

Thanks in advance for any suggestions you can provide.

Accepted answers

Joseph Chung Yin

@Durell Demartini -

Give this a try instead of using "=" use "in" in your query configuration.

I do know that currently there is a case where passing in multiple values from a custom field, it is not possible to obtain all related objects from Insight(Assets) schema. From Atlassian Support Team - "Insight is not capable of setting the values for the second custom field if the first custom field has more than one value. This is currently an Insight limitation, unfortunately."

I am not aware if Atlassian has fixed this limitation yet. Here is a similar case that is related/similar to this topic - https://jira.atlassian.com/browse/JSDSERVER-8521

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

All comments

Joseph Chung Yin

@Durell Demartini -

Give this a try instead of using "=" use "in" in your query configuration.

I am not aware if Atlassian has fixed this limitation yet. Here is a similar case that is related/similar to this topic - https://jira.atlassian.com/browse/JSDSERVER-8521

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

Durell Demartini

Hi @Joseph Chung Yin Thanks for the information. I tried your suggestion, but we still see the same behavior:

"Entity" IN ${customfield_12345.label}

Thanks very much anyway. I think what you passed along from Atlassian support pretty much answers our question:

"Insight is not capable of setting the values for the second custom field if the first custom field has more than one value. This is currently an Insight limitation, unfortunately."

Joseph Chung Yin

@Durell Demartini -

Excellent. I am glad that I can assist.

If my suggestion helped you, please remember to click on "Accept answer" when you have chance. So others with similar questions will see this posting as an anwser.

Best, Joseph

Paul Biagio

Here is the solution for how to achieve this: https://confluence.atlassian.com/jirakb/how-to-filter-assets-object-within-a-issue-based-on-other-object-custom-field-storing-multiple-objects-1142453352.html

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-service-management

jira-service-management-server