Insight: Is it possible to use fields from Portal, as placeholders in Insight Custom Fields

[Igor Muravsky]

I have few use cases, where I want to build more intelligent forms at Jira SM Portal. To do so, I'd like to use values of one Insight Custom Field in query of another Insight Custom field. Reference fields will not work, as there is no direct outbound or inbound references between objects. 

Documentation is quite vague in this regard and specify only general ability to use some custom fields in queries as placeholders. But it's not clear if Support Portal form fields can be used and if so, if Insight Custom Fields can be used and how.

I've done some tests using documentation examples, but without result. 

[Pier-Olivier Tremblay]

Hi Igor,

Since you are refering to "Referenced fields", I assume you are working on DataCenter version ?

[Igor Muravsky]

Yes, exactly. I'm using Jira SM DC edition.

[Pier-Olivier Tremblay]

Ok.

You are quite limited when it comes to cascading Insight fields without relations. You can specify a filter in the Ingisht field configuration and add a "Filter issue scope (IQL)" and refer to the other Insight field by using ${FieldName} but you can't access custom attributes.

Can you explain the exact goal and why are the object not related to each other? Perhaps the solution is in the datamodel and not in the fields configurations !

[Igor Muravsky]

Well, there are basically 2 problems.

1. Data model, when 2 objects doesn't have direct relations, but related through third object. Example: vCenter Datacenter -> Cluster -> Root Resource Pool -> Resource Pool.

I had and idea, that select query could use value of Datacenter field in Resource Pool field to select proper subset of values.

But in this case it's probably easier to add Datacenter link to Resource pool.

2. General question on usage of placeholders in Support Portal with Insight Custom Fields. You were referring to placeholder usage in "Filter issue scope (IQL)" and placeholders. Can you, please clarify if and how I can achieve something like this on Support Portal:

- Select Datacenter from Insight Custom field.

- Use value of Datacenter field, as text in filtering Resource Pools. Something like adding filter in issue scope: Datacenter = ${customfield_12345}

[Igor Muravsky]

Thanks for pointing in right direction. Found how to achieve what I need myself. 

Issue Filter Scope IQL like: Key = ${customfield_12345.key} or variations of this in different combinations, depending on need.

[Pier-Olivier Tremblay]

Glad you found a way.

Let me suggest something else that I used for a similar usecase where we had to display to an user a list of tasks, related to a project, related to an organization to which the user is related.

If your objects are related by third party objects, you can go up the chain with something like :

objectType = "Resource Pools" AND object HAVING outboundReferences(objectType = "Root Resource Pool" AND object HAVING outboundReferences(objectType = Cluster AND parentvCenter = ${customfield_12345}))

Assuming your object Cluster has an attribute referencing the vCenter in to which it is related. Otherwise you can nest another level of outboundReference.

You may aloso need to use inboundReferences instead of outboundReferences depending how your datamodel is configured.