The Update linked issue or sub-task post function of JWT DC is also available for JWT Cloud, with minor differences in terms of parameters and options.
The table below shows the detailed mapping between JWT DC and JWT Cloud.
Migration steps
Reconfigure the post function with the help of the following list, providing the necessary basics.
Migration details
JWT DC parameter | JWT DC parameter options | JWT Cloud parameter options | Notes |
---|---|---|---|
Fields | The following expandable list shows which JWT DC fields are available on JWT Cloud as well. | ||
Write protection | - | ||
Filter | Filter by project | Filter by project | |
Fileter by link type | Filter by link type | ||
Filter by issue type | Filter by issue type | ||
Filter by status | Filter by status | ||
Filter by field value | Filter by field value
| The list of available field codes and parser functions differs between JWT DC and JWT Cloud. | |
Additional Options | Update sub-tasks matching the specified filter criteria | Update sub-tasks matching the specified filter criteria | |
Update sibling sub-tasks matching the specified filter criteria | Update sibling sub-tasks matching the specified filter criteria | ||
Update recursively linked issues or sub-tasks matching the specified filter criteria | - | ||
Send email notification | - | ||
Update issue immediately | - | ||
Conditional execution |
| The list of available field codes and parser functions differs between JWT DC and JWT Cloud. | |
Run as | A drop down menu where you can select a field (all available Fields are listed) The default is Current user | The options are equivalent to the ones in JWT DC but split in two separate entries:
The default is the same as in JWT DC: Current user | Since only those fields can be selected which hold a user it may happen that the field code from JWT DC cannot be mapped to the respective field in JWT Cloud. |
If you still have questions, feel free to refer to our support team.