SIL: How to get values of custom fields defined in a list

Hello!

We had a question in Moscow Atlassian User group on how to get the value of a custom field in SIL if the name of the field is defined in an array.

I think code will explain it better:

string [] keys = selectIssues("key = SCRUM-22");
string [] fields = {"my text field"};
for (string k in keys) {
    for (string field in fields) {
        runnerLog(k.#{field});
    }
}

As you can see I get issues by a JQL query. Then I define an array of the names of fields which values I want to print out for selected issues. Then I iterate over all issues and inside this loop I iterate over all fields in the fields array and print out the value.

If I try to compile this code I will get an error:

The error is for this line:

runnerLog(k.#{field});

SIL tries to find a field with the name “field” (SIL does understand that “field” is a variable, it looks for a field with the name “field”) and SIL can not find such field and throws an error.

If we change this line with this one:

runnerLog(k.#{my text field});

Then everything will compile correctly and we will get what we want. Does it mean that we can not define names of custom fields in an array, instead we should always provide implicit names? Imagine we have 50 fields to select. In this case our code will look awful.

The answer is there is a way to make it clean.

SIL has this symbol %. If you surround a variable with this symbol, then SIL will treat this variable as a variable. It is needed in ambiguous situations like ours.

Let’s surround the field variable with the % symbol like this:

runnerLog(k.#{%field%});

Here is the complete code:

string [] keys = selectIssues("key = SCRUM-22");
string [] fields = {"my text field"};
for (string k in keys) {
    for (string field in fields) {
        runnerLog(k.#{%field%});
    }
}

Now this code compiles and works as expected.

Leave a Reply

%d bloggers like this: