Date: Fri, 29 Mar 2024 00:28:38 +0100 (CET) Message-ID: <1443564244.440.1711668518915@apps-confluence-5.apps-confluence.apps.svc.cluster.local> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_439_867968880.1711668518914" ------=_Part_439_867968880.1711668518914 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Keeping parent issues and sub-tasks in sync= , as described in this use case, is a lot of manua= l work. This automation rule will update the status of all sub-tasks based = on the parent status: When the parent iss= ue is rejected, all sub-tasks are also being rejected.
Create a new rule and name= it appropriately.
Providing a description will help you to identify what the rule does but= this step is optional.
Add a Trigger =E2=86=92 Issue transitioned= event
No further configuration needed. The automation rule is triggered every = time an issue is being transitioned.
Add a Condition =E2=86=92 =
Boolean Condition
Use the following Parser Expr= ession:
%{trigge= r.issue.status} =3D "Rejected"
Next to the Boolean Condition click on Add =E2=86=92 Selector&nbs= p;=E2=86=92 Issue Selector
Choose Sub-tasks
Next to the Issue Selector click on Add =E2=86=92 Action =E2=86=92 Transition issue
Transition to status
Choose Rejected
Enable the rule by clicking on the Enable butto= n =E2=86=92
This is how the configuration above should look on your screen
If you still have questions, feel = free to refer to our support team.