Get started

Use case library

JWT expression editor

JWT expression parser functions

JWT remote actions

Cloud migration hub

Additional product info

The Transition issue 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 Transition issue 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).

ModeExecute transition

Execute transition

Both JWT DC and JWT Cloud offer the opportunity not only to select a given transition but to define the transition which has to be executed by entering a parser expression. In that case, choose General parsing mode and insert the rebuilt   p arser expression   according to  Migrate JWT Parser expressions.

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

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

Transition to status

Transition to status

Both JWT DC and JWT Cloud offer the opportunity not only to select a givenstatus but to define the target status by entering a parser expression. In that case, choose General parsing mode and insert the rebuilt p arser expression according to Migrate JWT Parser expressions.

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

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

Additional options

Ignore conditions



Not available in JWT Cloud.

Ignore validators


Not available in JWT Cloud.

Ignore project permissions


Not available in JWT Cloud.

Delayed execution

Delayed execution

In JWT Cloud this parameter is not an option of Additional options (because they are not availbale in JWT Cloud), but can be found on the same level as the other parameters.

Conditional execution


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

Run as

Selected user, where you can pick a specific user

Selected user, where you can pick a specific user

The options are equivalent to the ones in JWT DC but split in two separate entries

Select a field (all available Fields are listed)

The default is Current 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 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.