Hello,
I am trying to build a rule(s) with the following logic:
We have an Issue Link Type created. Outward link: "child of". Inward link: "parent of". (This is not a replacement for the standard Jira hierarchy; it has a different context.)
We have project ABC and tickets in this project hold links "parent of" of tickets from projects DEF1 and DEF2.
The logic should say that anytime there is an unresolved DEF ticket, the parent ABD is in status Stable. Anytime all children from DEF projects are resolved the ABC ticket should go to Stable status.
I was able to build a rule saying that anytime the resolution value changes on any DEF ticket it checks resolution of all the other children and adjust the ABC status accordingly.
I was able to apply similar rule for scenario when a DEF ticket is linked to ABC ticket. But I struggle with a scenario when the DEF ticket is unlinked as I lose the reference of the unlinked ticket.
But maybe I am overcomplicating it. Can you think about a simple and elegant solution for this scenario?
Thanks for your help
if you create another automation rule and use the trigger "when issue link deleted", that should help with the delinking scenario(s).
You will need to rely on smart values
{{issue}} will always refer to the source issue, so if ISSUE-A is blocked by ISSUE-B, this rule will execute on ISSUE-B. To access ISSUE-A, use {{destinationIssue}}, and to access the link type, use {{linkType}}
Let me know if this helps in your automation rule
Helo, yeah, I read this in the documentation. In this case I was just sure how to use the smart values in the reference. However, I found the Destination issue value in the fork options, which solved the issue.
Thanks for trying to help here.
L.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.