How can I check if all the Linked Issues or child issues are closed/resolved or not ?

[Shrikant]

Hi ,

I have the requirement to check when all the linked issues are resolved, then the  parent issue should be resolved.

I tired using the automation for JIRA but the problem is it is not checking for all the linked issues even if one of the linked issue is resolved the automation rule triggers and resolves the parent issue.

Could you please let me know how to check for all the linked issues and not only ONE ?

 I want to check for all the Linked Issues or child issues and when ALL the linked issues or child issues are resolved then only the parent should be resolved 

pfa image for my automation rule.

[Mikael Sandberg · Accepted solution]

The automation you tested is misconfigured, because it will transition issues based on your schedule and ignore the branch. What you are looking for is something like this:

This one is an example from the Automation library, just change the parent branch to be the linked parent instead.

[Shrikant]

@Mikael Sandberg 

Hi Mikale

That does not work, I have tried for linked issue but its not checking for all the linked issues even if any one of the linked issue is resolved /closed it Resolves/Closed the Parent Issue.

[Mikael Sandberg]

Did you use the linked issues branch rule? That one will process all linked issues similar to this automation in the library:

As you can see from this example what you want do do to the linked issues has to happen within that branch. If you compare this to the rule you tried, in your rule the transition is for the issue that triggered the rule, not the linked issues like in the example above.

[shrikant maheshwari]

@Mikael Sandberg 

Hi Mikael,

So the requirement is I have an X Project and whatever issues I have in that project if they have any linked issues from any other project say Y or Z.

Then once all the linked issues are resolved from the projects Y and Z then automatically the corresponding issue from  X  project should also be resolved.

I have X project which has ISSUE KEY X-1

Now I have projects Y and Z which has Issue Key Y-1 and Z-1.

Y-1 and Z-1 are linked to X-1.

Now as soon as when Y-1 and Z-1 are resolved then automatically X-1 should be resolved.

If I choose what you suggested this does not work. Could you share the screen shot where the above case works

[Mikael Sandberg]

So based on your requirements the automation would look something like this:

This one checks the status on the blocked issue (in your case X-1) and that both Y-1 and Z-1 are in the status Done and if so, move X-1 to done as well.

[shrikant maheshwari]

@Mikael Sandberg 

Hi Mikael,

Thanks a lot it worked but just need one more help from you .

I have an Initiative and its child issues are epic so once any of the Epic is "In Progress",  I want Initiative to also move to "In Progress". I have written the below rules but both the rules are not working, could you please help -

RULE - 1

RULE - 2

[Mikael Sandberg]

You cannot use the parent branch to do this, since parent only applies to subtasks, and the parent epic only applies to stories/tasks linked to an epic. In this case you have to use the linked issues option.

[Shrikant]

@Mikael Sandberg 

but how do i get Initiatives using Linked issues . I tired using Linked issues but unable to get the Initiatives corresponding to Epics. Could you please share the screen shot of the automation

[Mikael Sandberg]

It would be similar to what I posted yesterday above. Instead of using the blocks link type that I used, you could specify your own link type to indicate the relationship between initiatives and epics. Then in the branch, check for that specific link type.

[Shrikant]

Actually the link between Initiative and Epic is through the child issues and I dont get that option in the Link type.

[Mikael Sandberg]

Okay, so you are using the Parent link field to link your epics to initiatives. So in that case you would have to create a smart value and use the JQL branch like this:

This is a very simplified example, I would add a check that the transitioned issue is an epic.

[Shrikant]

Hi Mikael,

I am not getting create variable option , i am using Automation for JIRA for data center

[Mikael Sandberg]

Then just skip that part and use the JQL branch, the smart value {{issue.Parent Link}} will give you the parent issue.

[Joe Stowell]

I'm not certain if this can be achieved by Automation but, we have something similar in the Workflows where when a ticket has a linked issue/sub-task, it can only be transitioned once the child tickets are completed.

I'm not sure if this can help you.