I have an automation that runs when a Parent ticket is updated with a Sprint value, all its linked issues also get updated with the same Sprint value
However, I want this to run for the linked issues within the linked issue as well and this is currently not happening
This is what it looks like
Parent issue-> Linked issue 1->Linked issue 2
I want the Sprint value for Linked Issue 2 to also change when the Parent issue is updated
Thanks in advance
Hi @Deepika
This is similar to the use case to update a Parent issue to the child and grandchild issues, and can be done with one rule.
However for your scenario, there is a risk of duplication between links and exceeding the branching limit of 100 issues. If you still want to try this approach, it could be like this:
Kind regards,
Bill
Hi @Deepika
I think two rules would be the most secure way to do this:
---
If you want Rule 2 to only activate if Linked Issue 1 was set due to the Parent, you could in a Condition to check for this.
For example, in Rule 2 you could...
---
Let us know your thoughts!
If you'd like more specific instructions on how to implement this, it'd be great to understand your current rule (if you've built one), and the exact relationship between Parent, Linked Issue 1, and Linked Issue 2 - eg. is it parent/child? Or linked issues? Etc
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can't next branches within branches, which is what you are trying to do. You probably need a second rule similar to the first that is also triggered by a change to the Sprint field. Instead of looking for children, you would branch on linked issues. You need to allow this rule to be triggered by another rule (a checkbox in the Rule Details section). This will allow the rule to cascade through the linked issues of the child and then all of the subsequent linked issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.