Get started

Use case library

JWT expression editor

JWT expression parser functions

JWT remote actions

Cloud migration hub

Additional product info

The Update or copy field values post function of JWT DC is also available for JWT Cloud (please note the different name 'Update fields'), 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 Update fields 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

Current issue

Parent issue

Parent issue
Sub-tasks

Select option Parser expression

  • General  parsing mode
  • Enter %{issue.subtasks} as parser expression

Not available in JWT Cloud but you can use a parser expression as described.

Sibling sub-tasks

Not available in JWT Cloud.

Linked issues

Select option Parser expression

  • General  parsing mode
  • Enter %{issue.links} as parser expression

Not available in JWT Cloud but you can use a parser expression as described.

Linked epic

Select option Parser expression

  • General  parsing mode
  • Enter %{parent.key} as parser expression

Not available in JWT Cloud but you can use a parser expression as described.

Issues under epic

Select option Parser expression

  • General  parsing mode
  • Enter %{issuesUnderEpic()} as parser expression

Not available in JWT Cloud but you can use a parser expression as described.

Sibling issues under epic

Select option Parser expression

  • General  parsing mode
  • Enter %{siblingIssuesUnderEpic()} as parser expression

Not available in JWT Cloud but you can use a parser expression as described.

Set target issues manually (parser expression)

Parser expression

In JWT Cloud, the parser expression has to return an issue key or an issue ID (or a list of them).

Fields




The expandable list below shows which JWT DC fields are available on JWT Cloud as well.

Fields

Please note that not all fields which can be set in JWT DC are available in JWT Cloud.

JWT DC field

JWT Cloud field

Notes
SummarySummary
DescriptionDescription
Affected versionsAffects version/s

This field requires a list of IDs of the values to be set.

AssigneeAssignee

An Atlassian account ID is expected.

Checkboxes (Custom field)Checkboxes

This field requires the ID of the value to be set.

ComponentsComponent/s

This field requires a list of IDs of the values to be set.

Date picker (Custom field)Date Picker
Date Time picker (Custom field)Date Time Picker
Due dateDue date
EnvironmentEnvironment
Epic link (Custom field)Epic link
Epic name (Custom field)Epic name
Fix versionsFix version/s

This field requires a list of IDs of the values to be set.

Group picker (Multiple groups) (Custom field)Group Picker (multiple groups)
Group picker Single group) (Custom field)Group Picker (single group)
Labels (Custom field)Labels (Custom field)
New labelsLabels
Number field (Custom field)Number Field
Original estimate (minutes) Original estimate (minutes)
Project picker (Custom field)Project Picker (single project)

This field requires the ID of the value to be set.

Radio buttons (Custom field)Radio Buttons

This field requires a list of IDs of the values to be set.

Remaining estimate (minutes) Remaining estimate (minutes)
ReporterReporter

An Atlassian account ID is expected.

ResolutionResolution
Security levelSecurity level

This field requires the ID of the value to be set.

Select list (cascading) (Custom field)Select list (cascading)

This field requires the IDs of the values to be set, e.g. 

Select list (multiple choices) (Custom field)Select List (multiple choices)

This field requires a list of IDs of the values to be set.

Select list (single choice) (Custom field)Select List (single choice)

This field requires the ID of the value to be set.

Sprint (Custom field)Sprint

This field requires the ID of the value to be set.

Story points (Custom field)Story point estimate
Text field (multi-line) (Custom field)Text Field (multi-line)
Text field (single line) (Custom field)Text field (single line)
URL field (Custom field)URL Field
User picker (multiple users) (Custom field)User Picker (multiple users)

A list of Atlassian account IDs is expected.

User picker (single user) (Custom field)User Picker (single user)

An Atlassian account ID is expected.

Version picker (multiple versions) (Custom field)Version Picker (multiple versions)

This field requires a list of IDs of the values to be set.

Version picker (single version) (Custom field)Version Picker (single version)

This field requires the ID of the value to be set.

Please find in the table below the mapping of the options for setting individual fields:

One important difference between JWT DC and JWT Cloud is that JWT Cloud uses IDs when setting fields like Checkboxes, Versions, Select lists etc. In those cases you have to care for

  • choosing the respective ID field from the fields offered by the field code injector (please note, that this value is already set as the default when choosing the option "Copy field value from...") or
  • writing a parser expression which returns the ID of the value which shall be set when choosing the option "Set field manually (parser expression)". For single values just enter the ID, e.g. 10001, for lists enter the list of IDs, e.g. 10001,10002,10010

In case of User fields, the Atlassian account ID has to be set.

The table above shows in the Notes which fields are concerned.

JWT DC option

JWT Cloud option

Notes 
Automatic-

Only available for the field Assignee.

Selected valueSelected value
Copy field value from current issueCopy field value from current issue

Select a field which returns a valid ID of the value which you like to set. The default for the field to be set is preselected (e.g. if you want to set the field Affects version/s, the field Affects version/s ID is preselected).

Set field manually (parser expression)

Set field manually (parser expression)

In JWTC the parser expression has to return the ID of the value which has to be set (in JWT DC it's the value). In case of field codes, you can just add .id to the field code in order to receive the respective id, e.g. %{issue.cf10004.id} or %{issue.components.id}.

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

Clear field valueClear field value
Write protection-
Additional Options

This parameter is not available in JWT Cloud.

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:

  • 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

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.