Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Insight custom field with issue scope IQL based on cascading select custom field

We have a cascaded select custom field.
We also have an Insight object field.
We want to set issue scope (IQL) for the insight object using placeholders for the first selection in the cascaded select field, but can't find the correct way.

We tried objectType =${customfield_10207.${1}} , objectType =${customfield_10207.${0}}, and other variations, but can't get the correct value.

For a particular issue, the value for the cascaded filed looks like this: [null:Domain name services, 1:Change domain] , where 'Domain name services' is the first select option, and 'Change domain' is the second option.

For regular select fields, the insight issue scope IQL works just fine as: objectType =${}

Please advise how to create the IQL correctly.

1 answer


Cascading list values are a hazzle. And I'm not sure Cascading fields are supported by placeholders and I don't get anything to work like your example. (

However, the syntax for multi-valued placeholders should be like this (with no dot): 

first item: ${customfield_10207${1}}

second item: ${customfield_10207${2}}

all items: ${customfield_10207${0}}


Would it not be possible to replace the cascading field with two Insight fields instead (one parent and one child field ) and that the child field value is referred by the field you are trying to filter?


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

319 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you