Page History
| Table of Contents | ||||
|---|---|---|---|---|
|
One of the greatest features of JWT lies in the accessibility of Jira data stored in system fields, custom fields and a great number of other, virtual fields that are made available by the JWT implementation. You can access, validate, do mathematical calculations and manipulate the values found in these fields through the use of field codes. Thesecodes are unique identifiers (keys) to all available fields.
Jira Workflow Toolbox uses field codes in many conditions, validators, post functions and calculated custom fields
.Field codes are used
to access
and manipulate datadata from:
- normal custom fields
- system fields
- virtual fields
- internal fields
- parent fields
Writable virtual fields
When a value is written into these fields, a feature or system field of the issue the field belongs to will be modified. These fields are also readable.
Values returned when reading virtual fields
- ephemeral text and number fields (temporary storage)
- parent fields available to all subtasks
- issue, project and user properties
For more detailed information on field availability and usage, please see the section on Virtual Fields.
Field codes are not only used as unique field identifiers, they are also an important safety feature for the Jira instance. Custom fields, for instance, can be renamed and the names do not have to be unique, but using JWT field codes makes your workflows and calculated custom fields immune to renaming.
You can choose the appropriate field codes by using the dop-down lists (for text and numeric fields) that JWT makes available whereever field codes could be needed as shown in the following screenshot:
After you've chosen the field, click on "Insert String Value" or "Insert Numeric Value" to insert the field code into the function you are configuring.
Please note that text strings are preceded by a "%" symbol, numeric or date/time codes are not.
After you save the function, the real field names will be displayed in the workflow or calculated custom field configuration.
For every virtual and custom field in a subtask, there is also another virtual field representing the same field in its parent issue, making it very easy to read and write parent's issue fields.
