How to loop through the lookup results and link each issue to some other, per criteria

[Inna S]

Hi, 

we are doing a migration of the large data set and need to link some issues. 

Unfortunately the trigger 'issue created' used to link every newly created issue to an existing one matching a criteria, hit the throttling limit and can't be used.

I was thinking of making a different automation, that would

- look up all the issues matching a criteria (e.g. no link of specific type is present or a field is empty)

- for every issue in the lookup result, create a link between the 'current' issue in the loop and the one with the one field value matching field value in the 'current' issue.

I'm having trouble iterating over the lookup results: added Log step to print the issue key but this doe not work as expected.

I then can't seem to find the way to link two issues when one of them is 

- not the trigger issue

- not a recently created issue

Is there a way to link just two arbitrary issues or full the system into treating the lookup result as a triggerIssue of a kind?

Thank you!

[Lavar Askew · Accepted solution]

I solved my problem. Renjith told me that I may have a circular dependency somewhere so that got me thinking about the pom files. I just went through and downloaded each jar, pom and sha1 file to my local repository and that is what worked for me.

[Joe Clark]

The settings you have specified (-Xmx and -XX:MaxPermSize) both control memory allocation on the heap. However, the error message you are seeing is a stack overflow error. The size of the stack is not related to the amount of memory allocated to the heap - it's a separate config.

While the broader question of why your JIRA build is getting a stack overflow remains a mystery to me, you can try brute-forcing through this problem by beefing up your maximum stack size. Use the "-Xss" parameter for this.

eg.

export MAVEN_OPTS=-Xss32m

[Lavar Askew]

Thanks for the reply Joseph. I tried increasing the maximum stack size, but the build process still breaks at Building Atlassian JIRA - Plugins - OAuth Service Provider SPI. I also noticed that I while I did have jta1.0.1.jar I did not have the pom file in my local repo. Not sure where to go from here. How can I see OAuth Service Provider SPI dependencies.

[taras19921]

In Windows:

set MAVEN_OPTS="-Xss32m"

You can create Environment variable with name: MAVEN_OPTS and value:  -Xss32m

[Deleted user]

This seems to be a bug in maven (both 2.0.11 and 2.2.1). Seen it with JIRA 5.2.10 myself again.