Why do scripted field scripts get executed at jira startup?

Question

Hey there,

i am currently developing some scripted fields on our jira test instance and was wondering why the underlying scripts get not only compiled, but also are executed at jira startup.

Interesting thing is even Issue issue = issue  contains, according to the logs, an real issue object.

That results in a flooded atlassian-log, cuz some methods for example "getLoggedInUser.getName" of course throw a NullPointerException.

This is not acceptable for production use.

One more thing to point out is that after deleting all issue index files and restarting, the scripts do not get executed.

What is going on here? Is Jira-/Scriptrunner trying to restore some old sessions? Is this some sort of caching? Is this some sort of default behaviour? And most important how can i turn it off?

Additional Information:

Jira Version: 7.x

Scriptrunner Version: 5.0.14

Scripts are on server in own script root folder

It looks like the script is not executed for all, but only some (random?) Issues

Daniel Yelamos [Adaptavist] · Accepted Answer

Hi Felix.

This is not intended behaviour. I can say with confidence that Scriptrunner does not do that by itself, and I can demo this in a vanilla instance for you whenever you want.

Things that could be causing this:

1. Rest request at the start of your instance to an issue that contains that scripted field.

2. Some kind of reindex at the start that forces recalculation of some subset of your scripted fields.

3. Another third party accessing an issue at the start.

If you feel like this is a bug in your instance I would advise you to raise a ticket in our customer support portal. We'd be glad to take a look.

If this solved your answer, please accept the answer so that other users know that this question has been solved.

May I help you further?

Cheers!

Dyelamos