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
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
I am trying to run programm on script runner console , it is getting time out after 2 minute.
Is there any option to increase the script runner execution time.??
Please check the online documentation on ScriptRunner for JIRA Cloud Limitations, especially execution length restrictions. You can find the link on the Settings page.
I'm afraid this is a complex one. A timeout is a combination of your browser, Atlassian Cloud, and Adaptavist's Scriptrunner services - mainly about the connections about the three of them, but it could also be what you are asking of SR to do.
If you have complex code that take a long time to run, then, SR will try to run it, but it is limited by Atlassian Cloud about how long it might take. SR can't do anything outside the Cloud limits.
2 minutes seems like a high timeout though. It's usually less!
Could you tell us what your code is trying to do?
Actually My code is trying to create various multiple issues with parent and child relationship[Each parent issue is containing around 15-20 child issues]. total count is 260 + records and in between of the program we are populating various fields like Description , summary and few custom fields in child issues. So is there any way we can increase the timeout on jira cloud. or to reduce execution time of our groovy script??
260 issues is a lot to do within the timeout periods for both Jira Cloud and Scriptrunner.
I think the main solution is going to have to be to split it up - create each parent issue (and its 15-20 issues) in one run of the script, not loads of parents.
You might be able to optimise the script, but if you've written it to be efficient, there's not much you can do there. But I'd still ask - the Scriptrunner support team might be able to take a quick look at it and see if it can be speeded up (If they're not going to be able, I'm happy to take a look too - feel free to name me if you do raise a support request along those lines, and they'll assign it to me)
You could also raise a support request to ask for the timeout on our side to be increased, which might help on the SR side, but it won't help if the problem is on the Jira Cloud side.