Migrate 'Compare two values condition'

The Compare two values condition of JWT DC is also available for JWT Cloud.

Since JWT field codes are not available in conditions or validators in JWT Cloud, but can implemented easily with replacing them by their Jira expression equivalent.

Migration steps

Add a Compare two values condition.

Reconfigure the condition with the help of the following list, providing the necessary basics.

Migration details

JWT DC parameter

JWT Cloud parameter

Notes

Left-hand side value

Field

Fields

The following list presents the fields supported by the Compare two values condition in JWT Cloud. Fields not appearing in this list, cannot be mapped to JWT Cloud. All fields are available for the contexts "issue" and "parent".

JWT DC field	JWT Cloud field
Affects version/s	Affects version/s
Assignee	Assignee
Attachments	Attachments
Component/s	Component/s
Creator	Creator
Date and time of creation	Date and time of creation
Date and time of last update	Date and time of last update
Date and time of resolution	Date and time of resolution
Description	Description
Due date	Due date
Environment	Environment
Fix version/s	Fix version/s
Issue key	Issue key
Keys of linked issues	Issue links
Issue status	Issue status
Issue type	Issue type
Labels	Labels
Original estimate (minutes)	Original estimate (minutes)
Priority	Priority
Project key	Project
Remaining estimate (minutes)	Remaining estimate (minutes)
Reporter	Reporter
Resolution	Resolution
Security level	Security level
Keys of sub-tasks	Subtasks
Summary	Summary
Total time spent (minutes)	Total time spent (minutes)
All custom field types	All custom field types provided by JWT DC except Text Field (read-only)

While this value is set by a parser expression in JWT DC, it is selected from a drop-down list in JWT Cloud.

Right-hand side value

Comparison value

Fields

The following list presents the fields supported by the Compare two values condition in JWT Cloud. Fields not appearing in this list, cannot be mapped to JWT Cloud. All fields are available for the contexts "issue" and "parent".

JWT DC field	JWT Cloud field
Affects version/s	Affects version/s
Assignee	Assignee
Attachments	Attachments
Component/s	Component/s
Creator	Creator
Date and time of creation	Date and time of creation
Date and time of last update	Date and time of last update
Date and time of resolution	Date and time of resolution
Description	Description
Due date	Due date
Environment	Environment
Fix version/s	Fix version/s
Issue key	Issue key
Keys of linked issues	Issue links
Issue status	Issue status
Issue type	Issue type
Labels	Labels
Original estimate (minutes)	Original estimate (minutes)
Priority	Priority
Project key	Project
Remaining estimate (minutes)	Remaining estimate (minutes)
Reporter	Reporter
Resolution	Resolution
Security level	Security level
Keys of sub-tasks	Subtasks
Summary	Summary
Total time spent (minutes)	Total time spent (minutes)
All custom field types	All custom field types provided by JWT DC except Text Field (read-only)

Either a field can be selected or a value can be set manually. In JWT Cloud one of these options has to be selected first and then a field or a value by using the parser expression editor has to be provided.

Operator

JWT DC operator	JWT Cloud operator
=	=
!=	!=
<	<
>	>
<=	<=
>=	>=

Depending on the field which is selected as left-hand value, not all operators are valid for this field. Only the valid ones are offered.

JWT Cloud offers the two additional operators ~ (contains) and !~ (does not contain) which may be used instead of the ones selected in the JWT DC configuration.

Due to the different architecture, it may happen that the condition gets too complex. This is the case when many fields are checked. The condition cannot be saved, and a corresponding error message will be displayed. If that's the case, the condition has to be split up into two or more.

If you still have questions, feel free to refer to our support team.

Content

Space Tools

Migration steps

Migration details