Hi all,
I'm using Insight to start to build an IT CMDB, which needs to includes a hierarchy of location data: Campus - Building - Location
These fields are on the customer portal and I want these fields to be filtered - eg when selecting campus 1, only buildings at campus 1 are available to select. When selecting building 2, only locations in building 2 are available to select.
Campus - has one or more buildings, linked via an inbound reference to buildings
Buildings - have multiple locations, linked via an inbound reference to locations
What I'm missing is some IQL to filter based upon the inbound/outbound references - can't figure out what is required.
Thanks in advance.
I ended up using the following IQL on the filter issue scope of the field to get what I needed:
"Building at Campus"=${Campus}
"Room/Location at Building"=${Building}
I had to directly reference as "customfield_xxxxxx" for it to work correctly.
Hi @Guy.Baxter
Check this tutorial on the atlassian website: https://confluence.atlassian.com/servicemanagementserver/adding-insight-custom-fields-to-screens-in-jira-1044784426.html
It explains in details how based on a selection from an initial insight customfield, the next customfield changes values.
Cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, thanks for the reply. The video was useful however it covers functionality that is not present in the cloud product.
I ended up using the following IQL on the filter issue scope of the field to get what I needed:
"Building at Campus"=${Campus}
"Room/Location at Building"=${Building}
I had to directly reference as "customfield_xxxxxx" for it to work correctly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.