The Condition on linked issues of JWT DC is not yet available in JWT Cloud, but can be implemented easily using a Jira expression condition. |
|
JWT DC | JWT DC option | JWT Cloud | Notes | ||
---|---|---|---|---|---|
Filter by link type | In line 1, add the issue link type names to be filtered to the list. | Example:
| |||
Filter by issue type | In line 2, add the issue type names to be filtered to the list. | Example:
| |||
Filter by status | In line 3, add the status names to be filtered to the list. | Example:
| |||
Filter by resolution | In line 4, add the resolution names to be filtered to the list. | Example:
| |||
Filter by project | Any project | Nothing to do! | |||
Current project | In line 5, add issue.project.key to the list | Example:
| |||
Any but current project | In line 5, add
| ||||
Set projects manually (parser expression) | In line 5, add project keys to be filtered to the list | Example:
| |||
Filter by field value | In line 6, 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, the fields available for an issue links can be found in IssueLink. | Examples:
| |||
Minimum number of linked issues | In line 7, change the minimum number of sub-tasks if necessary (the default is set to 0) | Example:
| |||
Maximum number of linked issues | In line 8, change the maximum number of sub-tasks if necessary (the default is set to1000) | Example:
| |||
Additional options | Allow unselected issue link types | In line 9, change the value to true, if you want to allow unselected link types. | Example:
| ||
Allow unselected issue types | In line 10, change the value to true, if you want to allow unselected issue types. | ||||
Allow unselected statuses | In line 11, change the value to true, if you want to allow unselected statuses. | Example:
| |||
Allow unselected resolutions | In line 12, change the value to true, if you want to allow unselected resolutions. | Example:
| |||
Allow unsatisfied field value filter | In line 13, change the value to true, if you want to allow an unsatisfied field value filter. | Example:
|
JWT DC parameter values | Jira expression | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Use case There must be at least one related Service Management request
|
| |||||||||||||||||||||
Use case Prevent transitioning when there is a blocking issue
|
| |||||||||||||||||||||
Use case All blocking issues must be resolved
|
|
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. |