Cascade in JPD by using a helper value field & child parent link automation

[Yannic Wolf]

Hi There, 

We are using JPD in our department

I am aware that as of now there is no easy way of cascading ideas under each other within a view. However, I am exploring a way that by using a custom helper value field to possibly achieve this. 

I have 2 fields: 

Custom select field: Top level Idea, Child level idea

Custom number field 'Helper value': 

The automation that I am trying to make is I think relatively simple but I am failing for the automation to do something and that could just be due to my limited programming knowledge. 

In my mind, a solution could be looking somewhere like this. The number you see is the helper value. So by sorting low to high on helper value you can make them be below their parent. 

In our business Top level ideas are only committed each quarter whereas child ideas are more frequently committed to. Even though this solution requires us to ensure that the parents helper value are in iterative order. We only commit to a few (10-15 ideas each quarter) so manually ensuring there is only one full number for each parent idea isn't much of a lift. 

The automation that I am attempting to do is basically:

Whenever an idea is linked to a parent then copy the helper value of the parent and fill in the child helper value with parent helper value + 0.1 

here the audit log: 

I am always getting the 'no related issues be found' and therefore the edit is not happening and I don't fully understand why. 

I am sure that it's just something missing 

[Bill Sheboy]

Hi @Yannic Wolf 

Based on the rule and audit log images you show, the link types do not match.  Links have "direction" and so there can be different link names for the different directions.  For example, "blocks" and "is blocked by".  Have you checked the link types are correct for both the trigger and the branch?

Kind regards,
Bill

[Yannic Wolf]

Hi @Bill Sheboy 

I see. So from what perspective am I looking at this 

The automation that I tested was from Child idea linking to parent 'is child of'. 

Let's say I go into the child idea and link the child as 'is child of' what your are saying the branch Linked issues should be 'is parent of' ? 

Also, that does sounds like I need two branches? 

One if the link is generated from the parents idea to the child and one if he link is from the child to the parent?

[Bill Sheboy]

Short answer: maybe.

For some scenarios, rules using the Issue Linked trigger with no link-types selected will use conditions and branching to handle different link directions.  It always depends on the scenario steps done by the person doing the linking.

• If your rule is triggering as expected with the "Contains" link-type in the trigger, next confirm what link-type should be checked for the branch, as those will be relative to the trigger issue.
• If you rule does not always trigger when expected, I recommend pausing to map out the link-types / directions, and when you expect the rule to run.  That will guide what is needed.