Automatically transition Epics AND Stories as sub-tasks transition?

[Lloyd Mangnall]

I'm currently using Automation for Jira Cloud, but I'm open to ANY solutions that will work in the Jira Cloud. I'm able to transition Epics when 1st-level child issuesTypes transition. I'm also able to transition the 1st-level child issueTypes when their sub-tasks transition. However, I'm unable to figure out a way to have the sub-task autotransition up through the hierarchy. Is it possible for the transition of a sub-task to automatically transition its parent issueType AND automatically transition the parent's corresponding parentEpic? 

Our use case is that Epics always have Issues, but Issues don't always have sub-tasks, so people-driven transitions could occur at either the issue or sub-task level.

If anySubTask -> In Progress
then anyParentIssue -> In Progress
then parentEpic -> In Progress

Also doing the same for Resolving the sub-tasks, issues & epics, but I assume solution would be basically the same if it is possible.

If allSubTask -> Done
then allParentIssue -> Done
then parentEpic -> Done

I have the same problem with Portfolio's custom "Parent Link", but I'll save that for another discussion.

[Maarten Cautreels]

Hi Lloyd, 

I've closed this question as it's a duplicate of https://community.atlassian.com/t5/Atlassian-Marketplace-questions/Automatically-transition-Epics-AND-Stories-as-sub-tasks/qaq-p/582997

I hope you don't mind.

Best,

Maarten