Issue Summary

When Jira serializes issue payloads for webhooks, all changelog entries for an issue are processed by default, regardless of the number of entries or the needs of the webhook consumer.

For issues with a long history, this can result in extremely slow webhook delivery, and excessive database load. There is currently no way to configure or limit the number of changelog items included in webhook payloads.

Steps to Reproduce

1. Create an issue and perform a large number of updates to generate a substantial changelog history.
2. Trigger a webhook (e.g., issue updated).
3. Observe the size of the webhook payload and the time taken to generate and deliver it.

Expected Results

Webhook payloads should include a configurable, reasonable number of changelog items.

Payload generation should be performant and scalable, regardless of issue history size.

Actual Results

All changelog entries are always processed for the webhook payload. For issues with extensive history, this leads to:

• Slow webhook delivery
• Increased database and network load

Workaround

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