Issue Summary

Starting with Bitbucket version 10.3, the format of timestamp fields in webhook payloads has changed. In prior versions, timestamps were represented in epoch milliseconds . From version 10.3 onwards, they are returned in ISO-8601 format .

Steps to Reproduce

1. Configure a webhook for any event on a Bitbucket Data Center instance running version 10.3 or later.

1. Trigger the corresponding repository event 
2. Inspect the webhook payload delivered to the configured endpoint.

Expected Results

Timestamp should use the epoch milliseconds format as below, consistent with versions prior to 10.3:

"createdDate": 1782914174484,
"updatedDate": 1782914174484, 

Actual Results

From Bitbucket version 10.3 onwards, timestamp fields are returned in ISO-8601 string format:

"createdDate": "2026-07-01T13:50:41.616Z",
"updatedDate": "2026-07-01T13:50:41.616Z", 

Workaround

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