Suggested improvements

• Autocomplete / syntax suggestions - Automation for JIRA provides Triggers like "Scheduled" and Action Items like "LookupIssues" that uses JQL to filter JIRA issues. However, unlike JIRA Advanced or Issue Navigator in each project, the JQL on Automation doesn't provide JQL smart syntax/input suggestion. Due to this the JQL query need to be built outside on the "Advanced Issue Search" page and then copied and tested in the Automation rule using the "Validate" button. This creates a uncomfortable UI experience while moving back and forth from the automation page.
• For Lookup issues actions, Jira is only able to get 100 issues. If query specified in JQL returns more than 100 issues, not all items will be considered. Only 100 item are returned, no matter if specified JQL query include more issues.
• 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. 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.