You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
A common question we get from people familiar with Insight on Server/DC is when will will Insight for Cloud support the ability to dynamically filter Insight custom fields.
Well, good news! Filter issue scope and placeholders are now available for Insight custom fields as part of the integrated version of Insight for Jira Service Management.
If you’re not familiar with filter issue scope, and wondering what on earth I’m on about, let me explain.
What is filter issue scope?
It’s a configuration option for Insight custom fields that lets you filter the objects shown in the custom field based on other values in the issue. This is done with a combination of IQL and placeholders that pull in the current reporter, assignee, project, summary, due date, custom field values etc.
And it works in the request portal too! You can dynamically filter Insight custom fields based on what’s already selected.
Why is filter issue scope useful?
Let’s say you have a list of laptops in Insight with an owner. When an employee wants to submit an issue involving their laptop you can have a custom field showing the laptops.
Without filter issue scope, the employee will see a list of all laptops, including those belonging to other people. With filter issue scope, you can make the custom field only show the laptops that the employee is the registered owner of which is much more user friendly.
How to configure - we set the filter issue scope to only show laptops with an Owner whose Jira User account matches that of the reporter of the issue.
”Owner” is an attribute on the “Laptop” object type in Insight which links to an “Employee“ object type.
”Jira user” is an attribute on the “Employee” object type that stores the Jira user profile of the employee.
Another example use case is for requesting new hardware. For example, if the requestor selects a model of laptop they want, another custom field can be used to show all laptops of that model type that are in stock in your inventory. So the agent doesn’t need to go into Insight to check available stock.
In this configuration, customfield_10236 is our custom field where the customer selects their desired laptop model.
Other common use cases for this, is to have a series of custom fields that narrow down a selection. For example, if you select an ‘affected application’ a following ‘affected infrastructure’ custom field could be set to only show configuration items that are related to the selected application.