Missed Team ’24? Catch up on announcements here.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Filter for issue scope in Insight for JSM

Mikael Sandberg
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 3, 2021

Anyone using the filter for issue scope to narrow down the selection of objects returned in an Insight field using a hidden field on the request form? I have tried both with a single line text field and a single select field, but none of those seems to work. The only time it works is if I explicitly specify the value. It was announced earlier this year that it is now available in Cloud, Announcing Filter Issue Scope for Insight.

Here is the configuration I am using:

Filter scope (IQL): objectType = Misc

Filter issue scope (IQL): Category.Name = ${customfield_10068.name}

Category is an object that is referenced in Misc.

1 answer

0 votes
Mick Szucs December 9, 2021

${customfield_10068.name} should only be necessary if customfield_10068 contains an Insight object - and it doesn't seem like it is possible to hide a field containing an insight object on a request type.

If you want the value of the field it should just be:  

Category.Name =  ${customfield_10068}

consistent with the final example on the page you linked.

(I think.)

Mick Szucs December 9, 2021

I did discover a weird behaviour that confused me while I was attempting something similar.  

Insight Lookup fields don't appear to work at all unless the Request Item I'm working with is assigned to a portal group.

Thought I'd mention it in case you are encountering the same behaviour.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events