Automation to update linked issue based on status

Question

Hello,

I am looking to create automation that is based on when a issue that is linked to an epic has a change in status to blocked/waiting or when it is overdue (due date) it triggers a status update to the epic to Blocked/Waiting.

A couple things I have tried so far are when an issue is linked and dont define the link type and the status equals Blocked/Waiting. Then search JQL for overdue tickets that are -30d and epic link is equal to the one I want to track. Then transition issue to blocked/waiting.

So far that is not working and I think it is due to the epic task relationship. Tried moving an issue that was linked into blocked and nothing occurred.

Mark Segall · Answer

Thanks for sharing.  I'm not 100% sure I understand what you're trying to accomplish, but I think there's two possibilities:

APPROACH #1

When an issue is transitioned to Blocked/Waiting, you want to transition the linked Epic(s) to the same:

* TRIGGER: Issue Transitioned To Blocked/Waiting
* CONDITION: Issue Type != Epic
* BRANCH: JQL* project = YOURPROJECT AND issueLink = {{issue}} AND dueDate >=-30d AND issueType = Epic AND status IN ("Awaiting Triage",Backlog,"Blocked/Review","In Progress","In Review","In Review/Waiting","Next Up",Waiting)

* ACTION: Transition Issue (Copy From Trigger Issue)

APPROACH #2

When an issue is transitioned to Blocked/Waiting, you want to transition the linked Epic(s) and all children

* TRIGGER: Issue Transitioned to Blocked/Waiting
* CONDITION: Issue Type != Epic
* ACTION: Lookup Issues* project = YOURPROJECT AND issueLink = {{issue}} AND dueDate >=-30d AND issueType = Epic AND status IN ("Awaiting Triage",Backlog,"Blocked/Review","In Progress","In Review","In Review/Waiting","Next Up",Waiting)

* ACTION: Create Variable* varEpic
* {{lookupIssues}}

* BRANCH (JQL)* "Epic Link" IN ({{varEpic}})

* ACTION: Transition Issue (Copy from Trigger Issue)

* BRANCH (Advanced): {{varEpic}}* ACTION: Transition Issue (Copy from Trigger Issue)

Clara Novalis · Answer

Mark Segall · Answer

Hi @Clara Novalis - Can you please share a screenshot of your rule?