[Insight] Traverse a relationship using ${ } (aka placeholders)

[Stephen Schaff]

Background

Here is the example schema:

• Application Group
• Application
  • Has an Application Group
• System Deployment
  • Has an Application Group
• Application Deployment
  • Has a System Deployment
  • Has an Application

So, I have Application Group called Order System.  It has three Applications called Order Search, Order Reports and Order Service.

• Order System
  • Order Search
  • Order Reports
  • Order Service

I now make a System Deployment called Order System 6.5.2 that is attached to the Application Group Order System.

• Order System 6.5.2
  • Order System

I then make an Application Deployment called Order Reports 5.2.1 and attach it to System Deployment Order System 6.5.2.

• Order Reports 5.2.1
  • Order System 6.5.2

Question

If I open up the Application Deployment Order Reports 5.2.1 and expand the drop down to select an Application, the drop down will has 300+ options because it is showing all Application objects.

I want to add a filter so that the Applications that show are only those that are referenced by the Application Group that is referenced in System Deployment Order System 6.5.2 that is referenced by the Application Deployment Order Reports 5.2.1 (the one I am picking an Application for).

So the end goal is that the drop down "chose options" for the Application field on the Application Deployment Order Reports 5.2.1 will be:

• Order Search
• Order Reports
• Order Service

And no other already existing applications will show.

-------

NOTE: this question is related: https://community.atlassian.com/t5/Jira-questions/Dot-notation-for-placeholders-in-insight/qaq-p/888702 But I could not seem to get my point accross asking for syntax help and the answers were not useful for this scenario.

[PJ Wysota]

Oh, nice You post the whole structure.

1. The point is You are not going 2 levels down the hatch, as You stated previously, but a bit more

Order Reports 5.2.1 -> Order System 6.5.2 (level 1) -> Order System (level 2) -> Applications (level 3)

So You need IQL with 3 levels depth query.

Then - as stated in linked topic: for one use case - using inbound backwards references - you got example for 2 levels query (working) - IF ALL references on above path are following - it would work by just extrapolating example.

In Your case (looking at structure above) I assume it is :

Order Reports 5.2.1 -> OUTBOUND -> Order System 6.5.2 (level 1) -> OUTBOUND -> Order System (level 2) -> INBOUND -> Applications (level 3)

To get from Order Reports 5.2.1 to Order System - solution provided would work. 

Then it is, as said in other topic, a bit more complex. And to be honest - it would require some tests (combining INBOUND with OUTBOUND), that, considering your wrong attitude against people trying to help You, are a bit too excessive.

And I promise not to reply anymore Your topics, if You don't appreciate support from community members.