In Jira automation, after a webhook triggers a JQL and lookup, issues transition and receive comments. However, the email action fires per issue. How can it be consolidated?
hey u can try setting a custom field to aggregate results then trigger a single email action, so instead of sending per issue it collects and sends at once. sort of like a bulk update in your automation.
I have experimented with a setup that triggers a secondary rule after the initial webhook-based automation runs. In my configuration, the first automation aggregates necessary details in a dedicated custom field on the project. Then, a scheduled rule reviews this field periodically and, when it detects updates, sends a single consolidated email that includes all the accumulated information. This method requires careful management of state to prevent duplicate notifications but has proven effective in dealing with scenarios where individual device notifications are unwieldy.
In my own experience, I’ve found that a periodic aggregation using a scheduled task works well. After the initial webhook and lookup, the strategy is to store the output in a temporary storage, such as a custom object or field accessible by a follow-up automation. Then, a scheduled process checks for this stored data at defined intervals and sends a single email with the collected details. This slightly more complex setup was initially challenging to configure but ultimately reduced the noise of repetitive notifications and improved clarity by sending a consolidated summary.
ya, try a script that batches the lookup results and sends one email once per cycle. it minimizes noise and is enlitghtening when dealing with many issues at once even though a bit custom setup is needed