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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I was wondering if the Escalation Services have the same limits on a server instance as they do on a cloud instance? In the cloud instance documentation it says that the JQL results are limited to 50 Issues. Is this the case on a Server as well?
Is the Escalation Service on a server instance run in parallel as it says in the jiracloud documentation?
If the there is a limit of 50 issues, what would you recommend I use instead if I may need to update 100+ issues?
Thank you for your question.
I can confirm that on ScriptRunner for Jira Server there is no limit set to how many issues which can be returned and updated by an escalation service.
However, we would advise keeping the number returned small as returning a large number of issues and performing an action on them could cause performance impacts to your server.
We would advise testing your escalation service on a clone of your production instance, in order to verify its performance before you run this in production.
If this response has answered your question can you please mark it as accepted so that other users can see it is correct when searching for similar answers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.