Summary

JQL doesn't have a feature to limit the number of issues returned from a search (equivalent to the SQL LIMIT or TOP clause). This means that if an automation rule acts on the results of a JQL search and if the number of issues returned exceeds 1000, the automation service limits are breached, leading to the rule getting throttled. This is especially problematic when many issues need to be updated, and the rule gets throttled, leading to a considerable wait time for the limit to be reset before rerunning the rule.

Suggestion

Provide the ability/mechanism for an automation rule to control or specify the number of issues it can update. This will allow users to execute a rule on over more than 1000 issues by limiting the number of issues on every subsequent run of the rule without getting throttled.