Memory and Scriptrunner


are there any known issues with using scriptrunner and memory usage?

We're getting outofmemory, and I know there could be lots of reasons, and just want to check in for scriptrunner/groovy issues. We have a lot of scripted fields and script workflow actions which will be invoked many times.

Are there any best practices for writing scripts?


1 answer

1 accepted

First of all check if you have varialbe declare into loops. For exmple

for(Issue subtask: issue.getSubTaskObjects()){
    CustomField field = ComponentAccessor.getCustomFieldManager().getCustomFieldObjectByName("field name")

It is better to change to:

CustomField field = ComponentAccessor.getCustomFieldManager().getCustomFieldObjectByName("field name");
for(Issue subtask: issue.getSubTaskObjects()){   

More - try not to use variable which used only once. For example:

IssueManager issueManager = ComponentAccessor.getIssueManager();
Issue issue = issueManager.getIssueObject()

It is better to use 

Issue issue = ComponentAccessor.getIssueManager().getIssueObject()

Thanks Vasily, I'll check through our code

Suggest an answer

Log in or Join to answer
Community showcase
Emilee Spencer
Published 6 hours ago in Marketplace Apps

Marketplace Spotlight: DeepAffects

Hello Atlassian Community! My name is Emilee, and I’m a Product Marketing Manager for the Marketplace team. Starting with this post, I'm kicking off a monthly series of Spotlights to highlight Ma...

30 views 0 3
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot