Dot notation for placeholders in insight

[Stephen Schaff]

A normal filter can be done like this

"Application Group" = ${Application Group}

But what if I need to go an object deeper in my relationship?  Something like this:

"Application Group" = ${System Deployment}."Application Group"

I have tried the above, and several variations, but nothing works. (It either does not pass validation or it gives an error, or does not match anything.)

Other variations I have tried:

"Application Group" = ${System Deployment}.${Application Group}

"Application Group" = ${System Deployment.Application Group}

"Application Group" = ${"System Deployment.Application Group"}

Is there a way to do this?

[Eric R Hartway]

Hi Stephen,

Did you ever find a solution to your problem?  I'm in need of accessing a referenced object's attribute value as well.  None of the dot notation variations I tested would work either.

Thank you,

Eric

[Stephen Schaff]

Not that I recall.  In fact I gave up on Insight altogether.

It was very close to being fantastic, but a few simple key features were missing.  Despite making feature requests they were ignored for years.

Over the years I have gotten occasional notifications as they indicate that they want to work on the requests and I think that one of them even got done.

But it multi-year responses are far too slow for me to wait for.  It was as if they had not tried to use their product in conjunction with the Atlassian suite of products and so were blind to the difficulties they were missing.

I recall being very frustrated about it at the time.  But I have long since abandoned Insight, so I am sorry to say that I don't have any real advice to give you.

[Eric R Hartway]

Well, that's unfortunate.  Thank you for the reply, Stephen.

[PJ Wysota]

As You are not referring to this, I cannot be sure what references You use: outbound or inbound. And there is a difference - look at this topic:

https://community.atlassian.com/t5/Jira-questions/Insight-referenced-field-indirect-referenced-object-2-tier/qaq-p/884409

where I posted some examples.

Then with variable to Field values:

- I am not sure if it would work exactly the same way for reference to field as with simpler case where you refer to 2-steps up/down object types references - it should be asked to Riada

- I assume your first notation is OK, but keep in mind that naming must be exact match with all references - so if attribute is named differently in current object scope and in referenced object scope - you should alter it.

Last point - general
- with using "" or not - I realised it using Insight post functions: 
-- when you use IQL queries - attributes are always coming with "" wile field variables - without it
-- however when you refer to attribute name in Insight PFs - use it without ""

[Stephen Schaff]

Thank you for your response.

I think you may have misunderstood my question.  The example you showed only shows a placeholder that accesses the immediate object.:

"Assigned To"."JIRA User" = ${Reporter}

In my scenario, the placeholder ${Reporter} needs to use a relationship to get the value to compare to.

Using that example I need to be able to so something like this:

${Reporter.Supervisor.Name}

But this does not work to get the relationship value.  Nor does any permutation that I can think of.

Is there a way to get placeholders to traverse relationships?

[PJ Wysota]

I looked at it our demo environments - of course this is one use case but:

1. Insight fields - as You see - I use 2nd level Ref field to not mismatch it:

2. This is object DNL1001 with some attributes refering to other objects:

3. A you can see we have a manufacturer here (Dell) but also in Model (as a attribute of model) and in OS (attribute of OS), and Installed Workplace Applications:

4. So basing on CIs affected - I want a Manufacturer information from either Model or OS or Application installed

And I got it - both Dell and Microsoft on the list in "2nd Level Reference" field.

The Filter Issue Scope I use in this case is like:

ObjectType = Manufacturers AND objects having inboundReferences(objects having inboundReferences(Key=${CIs affected}))

To have it unique - of course You would need anything like unique attribute name. Plus this is a case for inbounds. For outbounds it would look differently But I assume it would work as well.

[Stephen Schaff]

Still confused.

As I understand the objects having key words, when used in a filter, is that they only work on the list that is being filtered.  

But if there is no connection to my base object (the one that is needing the pick from the list), then you cannot connect them with out using somekind of reference traversing for the value in the ${ }.

None of the examples you show do that.  That is what my question is.  How can I traverse a relationship with the value that resolved from the ${ }?

[PJ Wysota]

Nope. If You are using flat attributes (Text, selects etc.) Obviously you will be limited to first level of references, as there are no more levels. 

But example above shows exactly the case to retrieve object at 2nd level. Then modifying the query (using different attribute than Key) you might retrieve other value.

And if Field config likethis is too difficult, go intro postfunctions, and create sequence od few postfunctions retrievery the data (same methods).