Filter issue scope (IQL) based on Jira Service Management Organization

Question

Hi,

I want users to be able to select Insight objects linked to the Organization they're a member of, usually this is only one.

Filter scope (IQL): objectType = Misc

Filter issue scope (IQL): Customer."Organization ID" = ${customfield_100xx.first.ID}

Where customfield_100xx equals the locked JSM Organization field.

The above doesn't work and there's barely any documentation about placeholders. Who has a working example?

Patrick van der Rijst_0n8q7n · Answer

I've implemented the following workaround;

Object type: Customer

Object type: Contact

Attributes:

- User (relates to Jira User)

- Customer (Object reference)

Object type: Application

Attributes:

- Customer (Object reference)

I've created two Insight custom fields;

- Customer

- Application

Customer having the following config set:

Filter scope (IQL): objectType = Customer

Filter issue scope (IQL):

object having inR(objecttype = Contact and User IN (${reporter}))

Allow search filtering by these attributes: Name

Object attributes to display on issue view: Name, Status

Field can store multiple objects: No

Display a default object when this field appears in a customer portal: Yes

Application having the following config set:

Filter scope (IQL): objectType = Application

Filter issue scope (IQL):

Customer = ${customfield_10037.label}

Allow search filtering by these attributes:Name

Object attributes to display on issue view: Name, URL

Field can store multiple objects: No

Display a default object when this field appears in a customer portal: No

Mark Segall · Answer

Hopefully we have an Insight ninja here in the community that can prove us wrong.  Would love to be able to do something with this use case.

Patrick van der Rijst_0n8q7n · Answer

Hi @Mark Segall

Yes I'm trying to use this during issue creation on the request form, I was hoping, like ${reporter}, there would be something known already as the organization but indeed I'm afraid this custom field is not available until the issue is actually created.