View Source

The Fields required condition of JWT DC is also available for JWT Cloud.

Since JWT DC field codes are not available in conditions or validators in JWT Cloud, they have to be replaced by their Jira expression equivalent.

Migration steps

Add a Fields required post function.

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

Migration details

Field parameter

The following list presents the fields supported by the Fields required 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 on JWT DC side except Text Field (read-only)

Both JWT DC and JWT Cloud allow to select a field out of the list and select the condition out of the following options:

Option	Description
is required	The specified field must have a value. If no value is present, the condition will fail.
must be empty	The specified field must not have a value. If a value is present, the condition will fail.

The option "All options required" is not available in JWT Cloud. This concerns fields like Checkboxes, User picker (multiple users), or Select list (multiple choices).

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.