Update dependencies Google Gson and jsoup to fix the following vulnerabilities:

• Gson: Deserialization of Untrusted Data
• jsoup: Denial of Service (DoS)

We've marked the app as being compatible with the read-only access mode.

Slack for Confluence is now compatible with Slack Blocks, a new way to format messages for Slack.

You can now only show the changed content in the Slack notification using the ${contentDiff} variable, e.g. in the "text" field of the configurable notification format in the global configuration of Slack for Confluence.

We had a bug (introduced with version 5.9.14) that only affected Confluence version 5.x which prevented the app from sending notifications to Slack.

If you've disabled sending notifications for pages having any view restrictions, it will now also disable notifications if a parent of that page has any view restrictions.

We're now sending notifications for inline comments, if the "Comment created/updated" checkboxes are active.

You can now disable sending notifications if the page or blogpost has any view restrictions in the general configuration.

You can now configure the user notification format for mentioned and task notifications.

This is also the first Data Center compatible release.

Update dependencies Google Gson and jsoup to fix the following vulnerabilities:

• Gson: Deserialization of Untrusted Data
• jsoup: Denial of Service (DoS)

We've marked the app as being compatible with the read-only access mode.

Slack for Confluence is now compatible with Slack Blocks, a new way to format messages for Slack.

You can now only show the changed content in the Slack notification using the ${contentDiff} variable, e.g. in the "text" field of the configurable notification format in the global configuration of Slack for Confluence.

We had a bug (introduced with version 5.9.14) that only affected Confluence version 5.9.x which prevented the app from sending notifications to Slack.

If you've disabled sending notifications for pages having any view restrictions, it will now also disable notifications if a parent of that page has any view restrictions.

We're now sending notifications for inline comments, if the "Comment created/updated" checkboxes are active.

You can now disable sending notifications if the page or blogpost has any view restrictions in the general configuration.

You can now configure the user notification format for mentioned and task notifications.

This is also the first Data Center compatible release.

Proxy settings are now automatically inherited from the Confluence proxy settings.

You can now use the new commentSnippet and commentFull variables, if you only want to include the content if a comment was changed. Those variables are empty if the change was not for a comment.

You can now configure a proxy server to send Slack notifications through.

(Originally released on Nov 7th.)

Since version 5.9_9 we're doing more extensive checks for the validity of the webhook URLs. Unfortunately we did this check every time when saving the space configuration, essentially making it required to "override" the webhook URL on every space.

The issue has been fixed and you no longer need to override the webhook URL in the space configuration.

We also had to adjust our version scheme, since Confluence had issues with upgrading to a version named 5.9_10.

You can now setup Slack for Confluence to notify you if you were mentioned on a page or if a task was added or changed. Get started by clicking on your Confluence avatar in the upper right-hand corner and select "Slack Notifications".

The version jump from 5.9_5 to 5.9_9 is due to our ongoing review of the Data Center version, which we hope to be able to release soon.

Improved Webhook documentation with note about ignoring the webhook channel.

Questions that were asked outside of a space did not properly send Slack notifications, which has been fixed.

For question notifications, the links to the question were no longer working in newer versions of Confluence, which has been fixed.

You can now send notifications to a different Slack instance by overriding the Slack webhook URL in a space.

• Notifications can now be sent for pages or blogposts with certain labels only.
• Questions for Confluence notifications introduced.
• Fixed an issue with space configurations that appeared in version 5.6_7.

Version 5.6_7 has been taken offline due to the issue mentioned above. Its release notes are stated below:

Notifications can now also be configured for a single Page or Blogpost, in addition to the already existing options to configure notifications for a Space or across all Spaces.

To use the new feature, just click on the three dots in the upper right-hand corner of a Page or Blogpost, choose "Slack Notification" and configure the desired channels and actions.

Also, we've added the variables "${contentSnippet}" and "${contentFull}" to be used in the Slack message. A list of available variables and their description can now be found in the global configuration as well.

You can now use new variables in the Slack Notification Format:

• ${pageContentSnippet} will be replaced with the first 140 characters of the page/blogpost/comment that was updated.
• ${pageContentFull} will be replaced with the full content of the page/blogpost/comment that was updated.

Also, the Space configuration for this addon is now also available in Personal Spaces, making it able to configure notifications for Personal Spaces specifically.

Under certain circumstances, it was possible that a Space configuration was affecting all other Spaces as well, sending unwanted notifications. This issue has been fixed and the Space configuration should now behave as expected.

Hide notifications if either

• The update is suppressed (respects the "Notify watchers" checkbox) - this was the default before, now it is configurable
• The update is made when the page is viewed (e.g. on task completion)

Both are configurable for either Global or Space notifications.