Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Is there a way to set the naming convention used in SIL scripts to reference Jira custom fields?

We currently use the Power Scripts plugin for Jira automation, along with their SIL scripts. Our scripts often reference Jira custom fields. In many online examples, Jira custom fields are referenced in these scripts using the naming convention customfieldname_1234 using the custom field's ID. However, in our scripts, we use a different naming convention. I have found another online example using a different naming convention that's similar to ours, but not exactly the same. Here's the link: SIL/Power scripts - How to set KPOtion (Power Cust... (
(The issue they're asking about at this link doesn't have to do with what I'm asking here; it's just to see an example of their naming convention for how they reference custom fields in these scripts.)

The fact that this naming convention is not exactly the same as ours, but also not the same as what seems to be the default, tells me that the naming convention was set specific to our organization, which must mean there is a way to set it in our instance of Power Scripts/Jira. Using the default (customfieldname_1234) worked for us as well, so whatever alternate naming convention is set in our system doesn't overwrite the default one, it just adds an extra option. Does anyone know where to find this? Does this all make sense?

1 answer

1 accepted

1 vote
Answer accepted

Take a look at Variable Resolution - Power Suite Apps for Jira 5.x - Confluence (

Custom Fields

Aside from the standard issue fields, you can also access custom fields from SIL selecting from the one of the following three ways:

  • by id, using the construct customfield_xxxxx - where xxxxx is the ID of the custom field.

  • by name - don't forget to use #{ and } if the name contains spaces.

  • by its alias.

Custom Fields Aliases - Power Suite Apps for Jira 5.x - Confluence (

Managing Aliases From the SIL Manager - Power Suite Apps for Jira 5.x - Confluence (


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 example looks with aliases.

Suggest an answer

Log in or Sign up to answer