Issue Summary

When a product event triggers webhooks in Jira, the payload is unnecessarily regenerated for each configured webhook, even though it remains identical, leading to unnecessary resource usage.

This impacts performance, especially in instances with a high number of configured webhooks listening to common events.

Steps to Reproduce

1. Configure a Jira instance with a significant number of webhooks (e.g., 500).
2. Ensure that a large subset of these webhooks (e.g., 300) are set to trigger on a specific product event, such as a "Issue Created" event.
3. Trigger the specified product event to initiate the webhook execution process.

Expected Results

The payload for the webhook should be generated once and reused for all webhook invocations, minimizing redundant operations and improving performance.

Actual Results

The supplier for generating the payload is called separately for each webhook invocation, resulting in excessive and redundant payload generation. This leads to performance bottlenecks due to numerous expensive operations, such as permission checks, being executed multiple times unnecessarily.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available