| Warning |
|---|
Looking for the documentation on the newest versions of SIL Engine and the Simple Issue Language for Jira 8 for Server/Data Center? Click here ! |
Contents
| Table of Contents |
|---|
...
This code is meaningless without comments as because the whole script purpose evades from the programmer's eye. A better option would be the following one:
...
Such coding style has the disadvantage that there might be more than one custom field with the Reported User name. In such cases SIL™ takes into account the first custom field resolved by name. Therefore, SIL™ has created its own custom field naming system, one that is independent of the IDs attributed by Jira to custom fields and one that can provide a much better distinction of the custom fields names. The feature is called SIL™ aliases, and allows you to alias any custom field with a friendly name. Let's see how this simple example looks with aliases.
...
Creating aliases is a simple task of editing the 'sil.aliases' properties file in the cPrime Home directory. This file must contain pairs in the following form: alias=customfield_id.
For our example above, we should edit it and put an entry like this:
| Code Block | ||
|---|---|---|
| ||
# custom fields aliases reportedUser=customfield_10001 |
| Note |
|---|
The sil.aliases file is located in the kepler directory inside of <JIRA_HOME>. This directory can be accessed from the SIL Manager by changing the View to be cPrime Home
|
You can rewrite the script in another way and use alias instead of the custom field ID or name:
...