Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Why do scripted field scripts get executed at jira startup? Edited

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

1 answer

1 accepted

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

Thanks for your reply and sorry for the late response @Daniel Yelamos [Adaptavist].
Ill take a deeper look into it and come back to you.


Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase

The benefits of using Jira in different departments

Jira is a great tool to use across different departments. Forget that paperwork – switch to Jira and get that tasks done smoothly. Marketing Jira allows for a complete digital transformation of you...

35 views 0 2
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you