Date: Thu, 28 Mar 2024 16:10:14 +0100 (CET) Message-ID: <119951040.350.1711638614435@apps-confluence-5.apps-confluence.apps.svc.cluster.local> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_349_1393043655.1711638614435" ------=_Part_349_1393043655.1711638614435 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
In Jira, work can be split up into several issues. One bigger task can b= e split up into several sub-tasks. For keeping track of the current status,= due dates can be used to indicate, when the issue should be finished. As n= ew sub-tasks are created and the work load increases, the due date of the p= arent issue might not be up-to-date anymore.
In the following use case we therefore are going to set the pare= nt issue's due date to the latest one among all sub-tasks.
Add the Upd= ate or copy field values post function to the create transition= of the sub-tasks' workflow.
This way the due date will be automatically updated as soon as a new sub= -task is created.
Choose Parent issue<= br>
Choose Due Date
Choose Set field value manually
max(fiel= dValue({issue.dueDate},siblingSubtasks()))
By using this expression, the latest due date within al= l sibling sub-tasks will be grabbed.
The used functions are:
If you still have questions, feel = free to refer to our support team.