Hi all,
I’m using Jira Cloud Automation with a scheduled rule that passes a JQL query into a Rovo AI agent. The agent analyzes each issue and writes an AI‑generated summary to a custom field.
The problem: when the agent executes the JQL, it consistently returns only 50 issues, even when the JQL matches many more. The execution log explicitly says it’s “returning 50 issues”.
As a result, only the first 50 issues are processed on each run.
Context:
Any guidance, documented limits, or architectural patterns would be appreciated.
Thanks
How many work items were you expecting to process?
A workaround would be to moving the primary JQL to the Scheduled Trigger and eliminate the rule branching, potentially allowing up to 999 work items...subject to your license level and service limits for automation:
https://support.atlassian.com/cloud-automation/docs/automation-service-limits/
Kind regards,
Bill
I do not think it is a hard limit on the automation or on the Agent, but Agent prompts can only handle a certain length before truncating. Can you try sending the JQL results to the Agent in batches? Yes, it will require multiple invocations to the Agent, but it may provide insight into how much you can pass to the Agent for processing at a time.
Another idea is to pass the JQL query to the Agent for processing. JQL queries are always preferable to long text entries.
I have successfully sent users or issues to an Agent in a CVS file, and it seems to process them in larger batches.
I hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.