This is impacting the Confluence Cloud for Slack app.

Issue Summary

When a page title is modified, other pages and blogposts have an update WebHook triggered. The way apps know the reason for that change looking at the attribute updatedTrigger.

Example of usage:

// Link refactoring is triggered when
// links to a renamed or moved page or attachment are updated
// Details https://goo.gl/85zTNa
if (req.body.updateTrigger === 'link_refactoring') return true 

However, blogposts do not contain the same attribute. I'd guess it's just a matter of having two pieces of code that are similar and then applying the same logic used in page updates to blogpost updates.

As a consequence, this issue leads apps like Confluence Cloud for Slack to inadvertently post update notifications to users that get confused since such change is not displayed in the content history.

Steps to Reproduce

1. Create page P
2. Create blogpost B containing a link to P
3. Setup WebHooks for a connect app (not sure about other types of WebHooks)
4. Rename page P or move it to a different space

Expected Results

WebHook payload contains an attribute updateTrigger with value link_refactoring.

Actual Results

Attribute updateTrigger is not present.

Workaround

None so far.