We are experiencing an issue with an SIL program that previously worked in our old JIRA version. We were using version 6.0.7 but recently upgraded to 6.3.15. Essentially the SIL program makes a new issue and assigns values based on the original issue. The error shown in the logs is: com.keplerrominfo.sil.lang.SILInfoException: [SIL Error on line: 37, column: 14] Field >><< cannot be matched against a standard field, a custom field or an alias. What is it?
On line 36 and 37 of the SIL program we have the following:
newIssueKey = createIssue(project, parent, "Jurisdictional Issue", summary, issue_priority, description, {}, "", "", issue_security_level, custom_fields_mapping); %newIssueKey%.assignee = currentUser();
We updated JJupin to version 3.0.3 since we updated our JIRA version, but we have not modified this program which worked fine. Has there been a change to JIRA or SIL between our old and new version that would prevent setting values the way that we are?
Hi Christopher,
It is a bug in the 3.0.3 version regarding substitution for cached scripts. We apologise for any inconvenience that this may have caused you. We have already developed a fix for it and the 3.0.4 release is expected to happen tomorrow. If it's urgent for you, you can disable the SIL caching from SIL Configuration page, but don't forget to enable it again after you do the upgrade to 3.0.4. With caching enabled, the SIL language is 2x to 10x faster.
Best regards,
Silviu
Hi Christopher, I just wanted to let you know that the 3.0.4 version is out, please upgrade and let us know if everything is back to normal.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.