How to change the status of a JSD ticket after the linked issue has changed status

[Dean Stearn]

Hi all

I've been trawling the web for hours and trying many different automations without much success, so I hope somebody can help me.. 

As I transition a ticket through JSD, I create a linked issue

For example JSD ticket is DEMO-123 and the linked issue created from it is DEMO-124

Demo-123 is sitting at status  PENDING with the next available status of RELEASED.

I am trying to create an automation rule so that DEMO-123 will change to RELEASED once DEMO-124 reaches a status of CLOSED

The audit log on my rule shows that the rule triggers when DEMO-124 reaches CLOSED but no updates are actioned.

I have stripped the rule right back to basics but for the life of me, I cannot get the parent issue to change status after the linked issue reaches the trigger status.

The intention is to create linked issues in other projects for our developers, so I thought it may be a permission issue. So for my tests I have been keeping the linked issue within the same project but still not happening.

Can somebody please help.

Thanks

Dean

[Jack Brickey · Accepted solution]

Which automation are you working with? I’m JSD there is “Automation” and there is “Project Automation”. Here is an example of one so have using “Automation”

and here is one I tested using Project Automation 

[Dean Stearn]

Thanks for the feedback Jack.

I am using Project Automation, tbh not sure what the difference is between them, is Automation to be phased out and replaced with Project Automation?

I'll have a go at your suggestions and let you know how I get on.

Thanks again...

Dean

[Dean Stearn]

Hi Jack

The first screenshot worked a treat.

The second screenshot, I am struggling to recreate the

       IF: Some Linked Issues Match        portion of the rule

Could you please expand how you achieved this?

Thanks

Dean

[Jack Brickey]

That is Related issues Condition.

[Dean Stearn]

Thanks Jack

The Project automation rule does not seem to work for me.

The parent issue still remains at its current status even after the linked issue as transition all the way through the process.

Below is what I have set up and the audit log shows a message about restrictions, however I cannot see how it would be restricted if the linked issue is within the same project.

Thaks

Dean

[Jack Brickey]

Why are you using “For parent” as the branch? That would be if you were dealing with sub-tasks. If you are dealing with linked issues then you should use the “For linked issues” branch function.

[Dean Stearn]

Thanks for all your help Jack, I selected Parent incorrectly and also spotted another issue that added to my problem.......

Thanks for the prompt responses, much appreciated....

regards

Dean