Migrate 'Add comment'

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

  1. Add the Add comment post function.

  2. Reconfigure the post function with the help of the following list, providing the necessary basics.

Migration details

JWT DC parameter

Unknown Attachment JWT DC parameter options

Unknown Attachment 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)

  • General parsing mode

  • Insert parser expression replacing JWT DC field codes with JWT Cloud field codes according to  Migrate field codes

The list of available field codes differs between JWT DC and JWT Cloud.

Copy field value from current issue

  • This option is handled as a parser expression in JWT Cloud

  • General parsing mode

  • Insert JWT Cloud field code of the respective field according to  Migrate field codes

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

Reply to customer


The configured comment author must have a user product role for Jira Service Management.

Internal comment for Jira Service Management projects


Add internal note




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 first two options are equivalent to the ones in JWT DC but split in two separate entries: Selected user and User in field.

As a third option you can also select the Jira Workflow Toolbox app user.

  • Jira Workflow Toolbox app user, user has admin rights, allowing execution of post functions that require admin privileges, even if the transition was triggered by a non-admin user

  • Selected user , where you can pick a specific user

  • User in field, where all User fields (e.g. Assignee or Project lead as well as all custom fields of the type User picker (single user) are listed

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.