Problem

Currently it is not possible to implement automations which require nested branch.

One use case is:

There is a parent issue with a subtask. The subtask has some linked issues. When workflow status of the parent issue changes to a particular status, the linked issues of the subtask should also change to those. if the parent issue status changes to X, that of the linked issues of the sub-task should also be X

Suggested Solution

Add the ability to have nested branches.

Why This Is Important

• If we include subtask in the branch, the actions will be performed on the sub-task and not the issues linked with the subtask.

• If we include Linked issues in the branch, then no branched issues will be found because the trigger issue does not have the linked issues but it's Subt-task do.

Workaround

Currently there is no known workaround for this behaviour. A workaround will be added here when available.