🚀 JWT 3.0 is out 🚀 

The app was completely overhauled, and so was the documentation: Jira Workflow Toolbox (Server/Data Center) Home

The page you are viewing is still valid for all app versions prior to 3.0.

One of the greatest features of Jira Workflow Toolbox is the easy accessibility to Jira data stored in system fields, custom fields and a great number of other, virtual fields that are made available by the Jira Workflow Toolbox implementation. You can access, validate, do mathematical calculations and manipulate the values found in these fields through the use of field codes.  These codes are unique identifiers (keys) to all available fields.

Jira Workflow Toolbox uses field codes in many conditions, validators, post functions and calculated custom fields to access data  from:

  • normal custom fields
  • system 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 Jira Workflow Toolbox 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 Jira Workflow Toolbox makes available wherever 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.