Skip to main content
Skip table of contents

Release notes of Slack Bitbucket notifier

5.06.29

Date:

Notable improvements are:

  • Improvement: Bitbucket 8 support.

3.30.24

Date:

Notable improvements are:

  • Improvement: Updated and added documentation links.

3.30.03

Date:

Notable improvements are:

  • Improvement: PR images preview in the configuration.

  • Improvement: Update 3rd party library dependencies to more secure versions.

3.28.12

Date:

Notable improvements are:

  • Improvement: When the App cannot access some required properties due to permission restrictions, it adds a small error section to the message and displays the information it could access.

3.25.11

Date:

Notable improvements are:

  • Bugfix: app had a conflict with a global body style.

3.24.23

Date:

Notable improvements are:

  • Bug fixes: avatar related bug fixes and improvements. Like Atlassian Bitbucket the avatars are taken from Gravatar service.

3.24.01

Date:

Notable improvements are:

  • New feature: Added scheduled notifications about new versions of Atlassian products like Jira, Confluence and Bitbucket.

  • New feature: Added scheduled notifications about new versions of Atlassian Marketplace applications.

  • A few minor bug fixes and reliability improvements.

3.22.08

Date:

Notable improvements are:

  • Added support on all levels of a setting “Add PR reviewers for minimal and compact pull request notifications“.

3.20.22

Date:

Notable improvements are:

  • Mattermost related improvements.

2.20.06

Date:

Notable improvements are:

  • 🎉 improved logging for sensitive information.

  • 🚀 you can use Slack threads to group pull request messages. More details are in our docs.

3.18.25

Date:

Notable improvements are:

  • Added a setting to hide pr reviewers for minimal size PR notifications.

3.18.03

Date:

Notable improvements are:

  • The reviewer added/removed events added.

  • Reviewers added to PR-related compact messages.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.