• The reviewer added/removed events added
• Reviewers added to PR-related compact messages.

• The reviewer added/removed events added
• Reviewers added to PR-related compact messages.

• Fixed compatibility issue with the official Slack App from Atlassian
• Webhook URLs Restricted to the Slack one only

• Fixed compatibility issue with the official Slack App from Atlassian
• Webhook URLs Restricted to the Slack one only

Updated 2 broken links:

• Now documentation lives at https://help.moveworkforward.com/SIWB/
• The Configuration button link was broken (just after the install). The issue was introduced recently.

No need to update otherwise.

Please reach out if you need any help with Slack and Bitbucket.

Updated 2 broken links:

• Now documentation lives at https://help.moveworkforward.com/SIWB/
• The Configuration button link was broken (just after the install). The issue was introduced recently.

No need to update otherwise.

Please reach out if you need any help with Slack and Bitbucket.

Move Work Forward's team is happy to release project level configuration support.

Here is a quick youtube video demo - https://www.youtube.com/watch?v=7ep8pYS0BIY

As always, please let us know your feedback, feature requests - https://www.moveworkforward.com/company

If you want to help us by leaving a 4-start review, please letting us know.

Move Work Forward's team is happy to release project level configuration support.

Here is a quick youtube video demo - https://www.youtube.com/watch?v=7ep8pYS0BIY

As always, please let us know your feedback, feature requests - https://www.moveworkforward.com/company

If you want to help us by leaving a 4-start review, please letting us know.

• Bug fixed: During migration between old version only the first 1000 repos were migrated.

• Bug fixed: During migration between old version only the first 1000 repos were migrated.

If you need any further help please do not hesitate to contact us.

If you need any further help please do not hesitate to contact us.

• Now in the compact mode (only) there is no commit list.

If you need any further help please reach out https://www.moveworkforward.com/company

• Now in the compact mode (only) there is no commit list.

If you need any further help please reach out https://www.moveworkforward.com/company

• Added support for source and destination branches configuration
• Added include and exclude filters for users and user groups
• Other Minor improvements

• Added support for source and destination branches configuration
• Added include and exclude filters for users and user groups
• Other Minor improvements

We are switching the payment model in order to support new development and support. You can still use older versions for free.

If you need any further functionality please let us know.

We are switching the payment model in order to support new development and support. You can still use older versions for free.

If you need any further functionality please let us know.

More improvements to come. Please let us know what problems this app can help solve you. Please contact us support@moveworkforward.com

• Bitbucket 5 supported
• Datacenter supported
• Need for work status on pull requests supported

Fixes: #39, #40

* Avoid NPE when deserializing settings

New Features:

• Branch name based slack channel selection. The format must be:PATTERN->CHANNELNAME,ANOTHERPATTERN->ANOTHERCHANNELNAME Example: bugfix/.*->#test-bf,master->#test-master
• Icon emoji added to the text if nonempty only for push events (note that icon url does not work).
• Trimmed white spaces for hook name to avoid issues

Fixes:

• pluginsettings was throwing errors on empty string values, fixed.

New features in 2.0.0:

• Updated stash2slack plugin for Atlasssian Bitbucket Server. This release is not working anymore with older stash releases (stash 3). Please upgrade to Bitbucket Server.

New features in 1.7.0:

• Disable notification for forks (#17). You can re-enable them by going to the slack settings for the private fork. By default, it is disabled on the global slack settings page.
• Changed Minimal notification level layout (#19)
• Differentiate tags from regular pushes (#20)

Hotfix release:

In v1.6, we have added a global channel name setting as well among with other settings (hook url was there already). However, we wanted the channel name and hook url behave the same, e.g.: if local hook url overrides the global one (that is, it is non-empty), it should not matter that the override flag is enabled, it should use the local settings. This was behaving incorrectly with the channel name setting in v1.6, now we fixed that.

• Add global configuration for notifications (#15): Now you have the ability to configure all options globally, and override them locally, if you wish. There is a new flag locally that turns on the override option. Also note that it is not required to enable the flag if you just want to override the channel name or hook url. However, you HAVE to edit the channel name if you enable the override flag (for hook url, this is still not needed).
• Verbose, Compact and Minimal notification levels for pull requests as well (#16)

New features in 1.5:

• Lowered Stash minimum version requirement from 3.6.1 to 3.5.0
• Ability control push message notification level: verbose, compact or minimal in the repository settings page.

• Ability posting to multiple Slack channels: use a comma separated list of channels names in this case (#8)
• Ability to control the granularity of the pull request activity (#10). NOTE: Existing instances will have ALL pull request events disabled when you upgrade, unless you enable some or all events again in the repo settings config page. This is because existing instances don't currently have the filter checkboxes prior 1.4, so all events will be ignored unless you go to the config and set them.
• Add richer information to pull request messages (#11)

Fixes and improvements:

• Use REPO_ADMIN privilege requirement on repo settings servlet (#7)
• Use value field in attachment in push messages (#6): slack does not index the title field for searching (they will fix this, but it is better to use the value field in the attachments)
• Branch delete is not informative (#4 and #5)
• If new branch is pushed, the entire history is sent to slack (#3)