nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

com.onresolve.jira.groovy.groovyrunner - variables scope

gil

Have a question on he custom listener. When there is a trigger as a result of a change such as a new version added, I put in some groovy code to process something. From what I understand, I assume that each trigger will trigger the code to run. All he code variables and objects are local to get trigger section, meaning if there is a second trigger, all variables and object in this second session is local and unique within this / each session? The declared variable value in session 1 can’t be seen / modified in other trigger sessions? And I assume that pass-in event object is local to each trigger call session?

Accepted answers

All comments

Nic Brough -Adaptavist-

That is broadly correct. A listener picks up "events", and the events in Jira (which are triggered by activity of varying sorts) contain a pile of information about what triggered it. They're independent of each other, so any given execution of a listener is based entirely on the data in its own event.

Nic Brough -Adaptavist-

That is broadly correct. A listener picks up events, and the events in Jira (which are triggered by activity of varying sorts) contain a pile of information about what triggered it. They're independent of each other, so any given execution of a listener is based entirely on the data in its own event.

gil

Thank you for the prompt reply, Nic. So I am experiencing some issue with the values obtained from the variable within a trigger session.

Basically, in the ScriptRunner custom listener, I get the JIRA version information (version name and its JIRA project key) from the event object triggered from a version creation from a JIRA project, and then create a new version in a separate JIRA project based on the obtained key/version. Everything is working fine, but at times, especially when there are concurrent, multiple creation of the JIRA versions, I got the incorrect key and version name and thus the wrong result. I suspect that the defined variables within each trigger session are not local, i.e. they could be static variable and thus being used in other trigger sessions. Below is a partial, sample code:

String sKey = event.version.projectObject.key;
String sVersion = event.version.name;
VersionManager vm = ComponentAccessor.getVersionManager();

if (event instanceof VersionCreateEvent){
try{
vm.createVersion(sKey + "-" + sVersion, null, null, 100101 ,null);

}
catch (Exception e) {

}
}

gil

I just ran couple more testing. In some cases, look like the version creation event is not even fired. As a result, the version creation is not captured and hence not added to the other project.

To sum up the issue - the problems are 1). wrong values received; 2). the triggers come with same value set which shouldn't be; 3). no trigger on certain events.

Aidan Derossett [Adaptavist]

Hey Gil!

ScriptRunner actually has a built-in listener specifically for this functionality. Have you tried testing with the Version Synchronizer listener to see if the same problem seems to be occurring?

Aidan

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

adaptavist

addon-com.onresolve.jira.groovy.groovyrunner