Tag
When a Jira automation rule doesn't run, check the rule's audit log first — it tells you whether the rule fired at all, fired and was filtered out by a condition, or failed with an error. From there the usual causes are: the rule is disabled, its scope is wrong, the trigger doesn't match, a condition is filtering everything, the actor lacks permission, or you've hit your plan's execution limit.
A scheduled Jira automation that sends one email per issue is almost always caused by putting JQL in the scheduled trigger itself. When the trigger matches issues directly, the rule runs once per matched issue. Move the JQL into a Lookup Issues action, leave the trigger's JQL empty, and loop over the results in a single email.
You can send a scheduled weekly summary email from Jira using a native Automation rule — no apps required. The trick most people miss: put your JQL in a Lookup Issues action, NOT in the scheduled trigger, or you'll get one email per issue instead of one summary. Here's the full setup, with the smart-value syntax for a clean issue list.
ClientLens for Jira