Deprecated function, available for Data Center only. Can be replaced in Cloud by the Updates fields post function. The table below shows the detailed mapping between these post functions and hosting options.
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. | ||
| Source field | Since the parameter Source field is not available in JWT Cloud, please proceed as follows:
| ||
| Mode | Replace issue description |
| Example: %{issue.cf10005}
The list of available field codes differs between JWT DC and JWT Cloud. |
| Add at the beginning of issue description | Choose the field to copy from (this is the field which corresponds to the parameter Source field in JWT DC) via the field injector of the parser expression editor and add %{issue.description} (preceded by an empty space) | The list of available field codes differs between JWT DC and JWT Cloud. Example: %{issue.dueDate} %{issue.description}
| |
| Add at the end of issue description | Enter %{issue.description} plus an empty space in the parser expression editor and choose the field to copy from (this is the field which corresponds to the parameter Source field in JWT DC)via the field injector of the parser expression editor. | The list of available field codes differs between JWT DC and JWT Cloud. Example %{issue.description} %{issue.dueDate}
| |
Run as | Only available in JWT Cloud. Use the default value User in field with the option Current user. In case the post function shall run with a different user, you can select any other option offered here. | ||
Conditional execution | Only available in JWT Cloud. Leave the parameter empty. In case you like to add acondition under which circumstances this post function is executed, you can enter it here using the Logical mode or the Jira expression mode of the JWT Cloud expression parser. |
If you still have questions, feel free to refer to our support team.
