You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Software Versions:
I'm utilizing scriptrunner scripts triggered as a post function of an Epic transition to generate a number of related Story issues. The general purpose of these scripts is to facilitate "templated" construction of pre-defined project steps defined by the created Stories. The script will iterate through an array of attributes to:
The scripts will create anywhere from 5 - 90 Story issues depending on the use case.
The issue I have encountered is that the process consumes all available database connections from Jira's database connection pool. This can effectively render Jira unusable during construction of the larger templates. It also appears to take up to several minutes for the connections to be released back into the pool upon completion of the script execution.
My question is this - is there a way to gate the number of database connections used from Jira's DB connection pool during execution of a Scriptrunner script? I'm less concerned with duration of script execution as I am with overall performance of Jira.