I have a Jira ticket - a parent.
And a few linked issues from several projects for the same parent.
How can I close the parent if ALL the linked issues are closed?
I was able to do it if only 1 ticket was linked to the parent, but when I have several I get stuck.
Thanks!
Hi @Alon Yehezkel Atlassian provides some Automation Templates that you can use. I found this one specific to closing the parent when the children are resolved that is probably pretty close to what you're trying to do.
Check it out here. From inside the application, when you're looking at your automations, there should be a Templates tab that will take you to the predefined templates. I've used several of those in my instance and then tweaked them to fit my application.
Hope that helps.
Hey @Alon Yehezkel ,
Welcome to the Atlassian Community!
Could you please share some additional information that might help suggest the best answer?
From what you've provided, I'd assume that you need the following high-level approach:
I hope that's helpful! Looking forward to hearing from you!
Cheers,
Thorsten
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Thorsten Letschert _Decadis AG_
Thank you for your help.
This is the automation currently working with 1 linked issue:
and this is example the use case I want to solve, in the picture below, when these 2 linked issues are in status "done" I need to change the status to "done" also the main task (BIP).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'd suggest the following approach:
I would generally recommend making all conditions and also the linked issues branch query as precise as possible to avoid producing false positives, e.g. by including the link type to the branching component, if this should only apply for blocking issues etc.
Please let me know if that solves your request.
Cheers,
Thorsten
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Additional hint: You might want to consider limiting the scope of the rule to "Multiple projects" and only selecting the "triggering" projects of interest to avoid unnecessary executions with regard to automation limits.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Thorsten Letschert _Decadis AG_ Thank you!
Unfortunately I tried this with and without the last linked issue condition - both are didn't work.
The main problem is when I tried to switch to the BIP, I can't reach to it.
Meaning I can only "see" it from the T3 bug as linked issue.
I need to actually to make my conditions on the BIP.
Because T3 will have only 1 linked issue (BIP) while the BIP will have several T3 linked issues
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Alon Yehezkel ,
If I understand your requirement correctly, this should work, removing your first "Linked issues match" condition. In your screenshot, there's an AND between the two, and an issue can't be of type "task" AND type "T3_Bug" simultaneously.
Within the branch, assuming your BIP ticket is returned within the "For: Linked issues" component, the components within the tree change "perspective" and the "Linked issues" condition is run against your BIP ticket.
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.