Page History
UI Text Box | ||||
---|---|---|---|---|
| ||||
The Condition on sub-tasks of JWT DC is not yet available in JWT Cloud Cloud, but can be implemented easily using a Jira expression condition. |
Migration steps
UI Steps | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
|
Migration details
JWT DC | JWT DC option | JWT Cloud | Notes | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Filter by issue type | In line 1, add the issue type names to be filtered to the list. | Example:
| |||||||||||||||
Filter by status | In line 2, add the status names to be filtered to the list. | Example:
| |||||||||||||||
Filter by resolution | In line 3, add the resolution names to be filtered to the list. | Example:
| |||||||||||||||
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:
| |||||||||||||||
Minimum number of sub-tasks | In line 5, change the minimum number of sub-tasks if necessary (the default is set to 0) | Example:
| |||||||||||||||
Maximum number of sub-tasks | In line 6, change the maximum number of sub-tasks if necessary (the default is set to1000) | Example:
| |||||||||||||||
Additional options | Allow unselected issue types | In line 7, change the value to true, if you want to allow unselected issue types. | Example:
| ||||||||||||||
Allow unselected statuses | In line 8, change the value to true, if you want to allow unselected statuses. | Example:
| |||||||||||||||
Allow unselected resolutions | In line 9, change the value to true, if you want to allow unselected resolutions. | Example:
| |||||||||||||||
Allow unsatisfied field value filter | In line 10, change the value to true, if you want to allow an unsatisfied field value filter. | Example:
|
Examples
JWT 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
|
|
UI Text Box | ||
---|---|---|
| ||
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. |
Excerpt Include | ||||||
---|---|---|---|---|---|---|
|