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... (atlassian.com)
(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?
