🚀 Effective since April 2020 and JWT version 2.9.0 Automation Toolbox for Jira is fully integrated into our top rated app Jira Workflow Toolbox (JWT)🚀

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

One of the greatest features of Automation Toolbox for Jira 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 Automation Toolbox for Jira 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.

Automation Toolbox for Jira uses field codes in Triggers, Conditions, Actions, and Selectors:

  • normal custom fields
  • system fields
  • parent fields available to all sub-tasks
  • 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 Automation Toolbox for Jira field codes make the fields you use in your rules immune to renaming. 

You can choose the appropriate field codes by using the drop-down lists  that Automation Toolbox for Jira makes available wherever parsed expressions are used.



     

The above example illustrates the configuration of a Field Changed Event trigger using the expression parser.  

1 - Choose the field
2 - Choose Value returned by parsed expression
3 - The drop-downs are auto-complete - just start entering the field you are searching for
4 - and click on one of the suggestions



    



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.