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. Thesecodes are unique identifiers (keys) to all available fields. Automation Toolbox for Jira uses field codes in Triggers, Conditions, Actions, and Selectors:
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. FieldCode Notationcode notationDepending on the context in which they are being used, field codes will contain a prefix according following this notation: {origin.object.attributattribute.method}. Available contexts in Automation Toolbox for Jira are:
%{trigger.issue.summarydescription} %{trigger.issueparent.reporter.emailsummary} %{trigger.issue.cf10021} %{system.currentUser}
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 %.
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)
Field codes in the documentationWherever field codes are used in the documentation they will be notated with 3 periods three periods (...) instead of prefixes.
Parsing ModesThere 2 parsing modes available:
k . Automatic parsing mode converter: Select Field ExampleThe examples below show expression usage in a Boolean Condition, but the usage rules are the same wherever fields are inserted into an expression. Click on Select field and then
The chosen field code will then be inserted into your parser expression where you can then enhance the expression with more
In the above examples, we've chosen to add a Boolean Condition validating that the Project key of the issue being processed is not (!=) TEST. After you save the function, the real field names will be displayed in the rule element. In contrast to systemor ATJ special virtual fields (which cannot be renamed), custom fields will be inserted into an expression with In this example, we've chosen the custom field "Sale Amount" to evaluate. In the expression, it is notated as cf10900. 10900 is Once the element is saved, it appears with its real name.
If at some point the field should be renamed i.e. Sale Amount Net, the expression will stay the same, but the element will now For more detailed information on field availability and parser usage, please see the section on Virtual Fields. |
CSS Stylesheet |
---|
#tocContainer { margin-right: 15px; position: fixed; right: 0; top: 160px; width: 23%; z-index: 1; } |
Div | |||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||
|