The Condition on sub-tasks of JWT DC is not yet available in JWT Cloud, but can be implemented easily using a Jira expression condition.
Migration steps
-
Add a Jira expression condition.
-
Build a matching Jira expression by migrating the parameters of the Condition on sub-tasks using this template:
JavaScriptlet ITI = []; let SI = []; let RI = []; let FVE = (issue => issue); let MI = 0; let MA = 1000; let ITA = false; let SA = false; let RA = false; let FVEA = false; let CON = (issue => ( (ITI.length == 0 || ITI.includes(issue?.issueType?.name)) && (SI.length == 0 || SI.includes(issue?.status?.name)) && (RI.length == 0 || RI.includes(issue?.resolution?.name)) && FVE(issue) )); issue.subtasks.filter(CON).length >= MI && issue.subtasks.filter(CON).length <= MA && issue.subtasks.every(issue => ( CON(issue) || (ITA && !ITI.includes(issue?.issueType?.name)) || (SA && !SI.includes(issue?.status?.name)) || (RA && !RI.includes(issue?.resolution?.name)) || (FVEA && !FVE(issue)) ))The following table shows how to obtain the individual components of the resulting Jira expression.
Migration details
|
Unknown Attachment JWT DC |
JWT DC option |
Unknown Attachment JWT Cloud |
Notes |
|---|---|---|---|
|
Filter by issue type |
|
In line 1, add the issue type names to be filtered to the list. |
Example: Bash
|
|
Filter by status |
|
In line 2, add the status names to be filtered to the list. |
Example: Bash
|
|
Filter by resolution |
|
In line 3, add the resolution names to be filtered to the list. |
Example: Bash
|
|
Filter by field value |
|
In line 4, adopt the function according to your needs by adding the respective Jira expression. It has to return a logical value. A list of field codes can be found in Field codes. For more information about Jira expression, please have a look at Atlassian's documentation. |
Examples: Bash
Bash
|
|
Minimum number of sub-tasks |
|
In line 5, change the minimum number of sub-tasks if necessary (the default is set to 0)
|
Example: Bash
|
|
Maximum number of sub-tasks |
|
In line 6, change the maximum number of sub-tasks if necessary (the default is set to1000) |
Example: Bash
|
|
Additional options
|
Allow unselected issue types |
In line 7, change the value to true, if you want to allow unselected issue types. |
Example: Bash
|
|
Allow unselected statuses |
In line 8, change the value to true, if you want to allow unselected statuses. |
Example: Bash
|
|
|
Allow unselected resolutions |
In line 9, change the value to true, if you want to allow unselected resolutions. |
Example: Bash
|
|
|
Allow unsatisfied field value filter |
In line 10, change the value to true, if you want to allow an unsatisfied field value filter. |
Example: Bash
|
Examples
|
Unknown AttachmentJWT DC parameter values |
Jira expression settings |
||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Use case All sub-tasks in the Closed status must have a specific resolution
|
|
||||||||||||||||
|
Use case Close parent issue only when all sub-tasks are closed
|
|
||||||||||||||||
|
Use case An issue must have at least 3 resolved Test Cases
|
|
Due to the different architecture, it may happen that the condition gets too complex. This is the case when many fields are checked. The condition cannot be saved, and a corresponding error message will be displayed. If that's the case, the condition has to be split up into two or more.