Date: Thu, 28 Mar 2024 21:10:14 +0000 (UTC) Message-ID: <111857928.7.1711660214691@ced7fbb13bb2> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_6_1198268233.1711660214690" ------=_Part_6_1198268233.1711660214690 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This sample scenario shows you how simple it is to add a JSU automation = rule to a workflow.
Let=E2=80=99s see how we use JSU to automate the task of closing multipl= e sub-tasks under a parent issue.
Here, we select the =E2=80=9CDone (21)=E2=80=9D in our = Task Management Workflow.
First, we select the Post Functions tab then click
We want to configure a linked transition so we select the Linked= transition (JSU) post function and then click A= dd at the bottom of the page.
Configure the parameters:
On the Trigger transition on all issues related as parameter, c= hoose Parent/Sub-task.
Select All sub-tasks (issue in Transition must be parent).
In the Transition drop-down menu, select Done (21) to ensure all sub-tasks would move to Done.
Select your desired resolution status from the Resolution drop-down= menu.
Click Add at the bottom of the page.
We have published our workflow, so now we need to set up an issue and cr= eate a few sub-tasks in our test project.
Next, we move the parent issue to Done and wa= tch as JSU automatically moves all sub-task statuses to Done!
Next, prepare your own test project and try it out for yourself. You can= find more examples of JSU in action in our use cases.