The Add comment 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
Add the Add comment post function.
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 |
---|---|---|---|
Target issue: Current issue | Only available in JWT Cloud. Please use the default value Current issue. | ||
Comment text | Add comment manually (parser expression) |
| The list of available field codes differs between JWT DC and JWT Cloud. |
Copy field value from current issue |
| The list of available field codes differs between JWT DC and JWT Cloud. | |
Comment visibility | Unrestricted (all users) | Unrestricted (all users) | |
Restricted to project role | Restricted to project role | The configured comment author must be a member of the configured role (see Add comment). | |
Restricted to group | Restricted to group | The configured comment author must be a member of the configured group (see Add comment). | |
Customer facing comment for Jira Service Management projects | Not available in JWT Cloud. | ||
Internal comment for Jira Service Management projects | Not available in JWT Cloud. | ||
Additional Options | Send email notification | Not available in JWT Cloud. | |
Conditional execution |
| ||
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 | This parameter is called Comment author in JWT Cloud. Since only those fields can be selected which hold a user it may happen that the value 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.