Jira Automation Rule - Moving Parent issue from Blocked to To Do when child issue is unblocked

[Gefrey Manohar]

Hello.

I am trying to set up an automation rule but having issues. I would like to transition the Parent issues from Blocked to To Do if their blocking children issues are transitioned from Blocked to Done. 

Any help is appreciated, thank you!

[Ste Wright]

Hi @Gefrey Manohar 

Can you clarify the relationship for more specific instructions - is it...

• A parent Task, with a child Sub-task?
• An Epic, with a child Task?
• A custom parental relationship, using the hierarchical levels in Advanced Roadmaps?

Please also confirm if...

• The Project is Team-managed or Company-managed

---

As an example, using Task as the parent, and Sub-task as the child, your rule might look something like this...

• Trigger: Issue Transitioned
  • From: Blocked
  • To: Done
• Condition: Issue Fields Condition
  • Field: Issue Type
  • Condition: Equals
  • Value: Sub-task
• Branch - Type = Parent
  • Sub-Condition: Related Issues Condition
    • Related Issues: Sub-tasks
    • Condition: None match specified JQL
    • JQL: status = Blocked
  • Sub-Action: Transition Issue
    • Destination: To Do

^ I've assumed that if more than one child is blocked, then the automated move of the parent should not happen - hence the Sub-Condition.

---

Let us know if this works for you, or provide us some additional information so we can provide more specific instructions :)

Ste

[Gefrey Manohar]

Hi @Ste Wright 

Thank you so much for your response. I would like to amend my initial requirement. I would like to create the automation rule to apply to a story blocking another story. It does not necessarily have to be a parent child relationship. 

For example, if Story 1 is in Blocked status because of story 2, when story 2 is marked done, I would like to automatically move Story 1 from 'Blocked' to 'To Do' 

Could you please help me with this? Thank you very much!

[Ste Wright]

Hi @Gefrey Manohar 

Sure - I'd modify some of the design choices for this...

• The rule needs to cater for a many-to-many relationship - i.e many Issues can block one Issue.
• The first condition will check for related issues, rather than Issue Type, as any Issue Type can be linked to any other using a sibling relationship
• The sub-condition is checking all Issues match the JQL, rather than none of them. This is because issues linked as blockers, could be in any Status. Also, all blockers should be Done before the blocked Issue can continue.

---

This is what I'd try...

• Trigger: Issue Transitioned
  • To: Done
• Condition: Related Issues Condition
  • Related Issues: Linked Issues
  • Link Types: blocks
  • Condition: Are present
• Branch - Type = Linked Issues (blocks)
  • Sub-Condition: Related Issues Condition
    • Related Issues: Linked Issues
    • Link Types: is blocked by
    • Condition: All match specified JQL
    • JQL: status = Done
  • Sub-Action: Transition Issue
    • Destination: To Do

---

Let us know if this works for you :)

Ste