Versions Compared

Old Version 2

changes.mady.by.user Shane Smith

Saved on

compared with

New Version Current

changes.mady.by.user Jonathan Muse

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Button handy
blanktrue
color#0052CC
nameSend Feedback
linkhttps://docs.google.com/forms/d/e/1FAIpQLScmToBe3vynAlb5fdKwCGxYqnTbDc66sIBgeecG2BuFDuHc7g/viewform?entry.2002826954=Managing+Aliases+in+the+sil.aliases+File+-+496206151
widthauto

Excerpt
hiddentrue

Creating aliases is a simple task of editing the 'sil.aliases' properties file in the Kepler Home directory.

Creating aliases is a simple task of editing the 'sil.aliases' properties file in the Kepler 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:

sil.aliases
Code Block
# custom fields aliases
reportedUser=customfield_10001
Warning

The sil.aliases file is NOT a SIL language file. It does not require a semi-colon and the end of each line. SIL syntax checker will not run for this file.

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 Kepler Home

You can rewrite the script in another way and use alias instead of the custom field ID or name:

Code Block
if(isNotNull(reportedUser)) {
  assignee=reportedUser;
}

  Now the code looks clean and the script function creator is clear even without comments.

The SIL Manager interface also uses the sil.aliases file. Saving changes from the SIL Manager will cause the sil.aliases file to be overwritten.

See More

Child pages (Children Display)
pageCustom Fields Aliases
We've encountered an issue exporting this macro. Please try exporting this page again later.