Date: Thu, 28 Mar 2024 15:28:04 +0100 (CET) Message-ID: <1840051235.344.1711636084661@apps-confluence-5.apps-confluence.apps.svc.cluster.local> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_343_1798043240.1711636084659" ------=_Part_343_1798043240.1711636084659 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This is an example of creation of multiple issues based= on seed strings using Create issues and sub-tasks pos= t-function.
We want to automatically create specific set of sub-tasks for each speci= fic component selected in current issue. In this particular example we want= to create the following sub-tasks for each component:
Component |
Sub-tasks |
---|---|
Character |
Model, Texture, Animation |
Landscape |
Illumination, Music |
Portrait |
Photo, Post-processing |
We want that each new sub-task remains unassigned, and that the reporter= is the user, who executes the transition in parent issue. The rest of the = fields in the new sub-tasks will inherit from parent issue.
We use Crea= te issues and sub-tasks post-function in a transition or = the workflow of parent issue with the following configuration:
We are using the following expressions:
(%{00094} ~ "Character" ? ["Mode=
l", "Texture", "Animation"] : []) UNION
(%{00094} ~ "Landsc=
ape" ? ["Illumination", "Music"] : []) UNION
(%{00094} ~ "P=
ortrait" ? ["Photo", "Post-processing"] : [])
"Sub-task for " + ^%
=
getMatchingValue(^%, ["Model", "T=
exture", "Animation", "Illumination", "Music", "Photo", "Post-processing"],=
["Create the model for the new character.",
"Create the =
animation for the new character.",
"Create the illumination=
for the new landscape.",
"Create the music for the new lan=
dscape",
"Do the photos for the portrait.",
"Do the post-processing of the portrait."])
%{00041} =3D =
null
Once configured, transition will look like this:
The workflow is shared between parent issue and sub-task, thus we are us=
ing Conditional execution with boolean expression =
%{00041} =3D null
to avoid the post-function to be ex=
ecuted by sub-tasks.
Note that: