Deprecation notice - Worklog data in issue-related events for webhooks

On March 1, 2017 we will be making changes to how worklog data is sent in webhooks, in JIRA Cloud only:

• The Issue webhook in JIRA will no longer contain worklog & comments objects in the issue representation (this mainly applies to the updated event)
• The **"worklog updated" **event for the Issue webhook will no longer be available
• The Worklog webhook in JIRA will now only include the 100 most recent items.

These features will be removed six months after this notice is published, as described in the Atlassian REST API Policy.

Why?

Currently worklog data is sent with the issue webhook by loading all worklogs to memory and serializing them to JSON. This presents a scalability issue when issues have a large number of worklogs.

This functionality also duplicates the richer worklog webhooks, which have more fine-grained events and are more concise.

Our intent is to give developers who need worklog data the specific objects they need, while making webhooks more reliable for everyone.

Replacement

If you currently use webhook objects from issue webhooks, you should migrate to listen for created, updated, and deleted events from the worklog webhook.

You can learn more about webhooks in the JIRA Cloud developer documentation: Webhooks - Atlassian Developers

You can report feature requests and bugs for JIRA Cloud and webhooks in the ACJIRA project on ecosystem.atlassian.net.