Page History
Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Excerpt |
---|
OverviewOne of the most important features of Automation Toolbox for Jira is the easy accessibility to Jira data stored in system fields, custom fields and a significant 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 |
and actions:
Field codes are not only used as unique field identifiers, but 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 expressions can be used. Field |
code notationDepending on the context in which they are being used, field codes will contain a prefix |
following this notation: {origin.field/data}. Available contexts (or origins) in Automation Toolbox for Jira are:
|
the origin (where the data should be read from / written to), is a referential part of the field code and will be inserted into the expression whenever you select a field from a dropdown list (as shown below).
|
|
|
|
|
Field codes: |
|
Field codes must always be enclosed by curly brackets (or braces) but if they are used for text-strings, the brackets must be preceded by a percent sign %.
|
|
fields can be referenced as numbers using the following notation: {somenumberfield}. |
( no preceding % sign)
|
being transformed to text, so any field can be referenced as a text-string value using the following notation: %{somefield}. Cascading Select or Multi-Cascading Select fields, where i is the index that represents the level to be accessed. (i = 0 is used for base level) |
are notated as %{somefield.i} .
Field |
codes in the documentationWherever field codes are used in the documentation they will be notated with |
three periods (...) instead of prefixes.
|
|
Parsing Modes
There 2 parsing modes available:
- Basic: with this simple parsing mode you can write free text and insert field codes with format %{nnnnn} or %{nnnnn.i} anywhere in your text. These field codes will be replaced at run-time with the corresponding field values in current issue.
Automatic parsing mode converter: You can write your text in basic mode, and then switch to advanced mode. The text to be parsed will be automatically rewritten as a string expression. Now, you can simply make the modifications you require, making use of text formatting functions, or inserting math or time expressions where needed.
Example of using field codesThe example below shows and |
k . Automatic parsing mode converter:
Select Field Example
The examples below showexpression usage in a Boolean Condition |
.
|
|
CSS Stylesheet |
---|
#tocContainer { margin-right: 15px; position: fixed; right: 0; top: 160px; width: 23%; z-index: 1; } |
Div | |||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||
|