Skip to main content
Skip table of contents

Release Notes

Release notes for Post Webhooks for Bitbucket.

Your feedback is very welcome, please do not hesitate to reach out at http://moveworkforward.com

20.0.0+

Notable improvements are:

  • Bitbucket 9 compatibility

Note: you may need to download the version manually from the Atlassian Marketplace.

7.03.09

Date:

Notable improvements are:

  • BUG: Big customer: Improved performance of the global page. Added pagination. Now the page does not load all rules on the load.

  • IMPROVEMENT: Add a flag that permits having multiple global webhook.

  • IMPROVEMENT: Added ability to override Bitbucket URL in the webhook payload.

  • IMPROVEMENT: Added settings to control the webhook retry policy.

7.02.04

Date:

Notable improvements are:

  • IMPROVEMENT: Added support for Pull request approved event.

4.12.16

Date:

Notable improvements are:

  • IMPROVEMENT: Improved performance and permissions check, which impacted huge instances.

4.12.08

Date: - Bitbucket 7+ support only

Notable improvements are:

  • DEPRECATED: support of Bitbucket 6.

  • ADDED: Azure DevOps pipeline parameters configuration.

3.33.27

Date:

Notable improvements are:

  • ADDED: request timeout has been added to the settings.

4.07.09

Date:

Notable improvements are:

  • Feature: Added commitMessage to outgoing APIs.

  • Feature: Improved UI interactions with the APIs.

4.06.22

Date:

Notable improvements are:

  • Feature: Bitbucket 8+ compatibility.

  • Feature: Data export and import.

  • Feature: Documentation improvements.

3.31.09

Date:

Notable improvements are:

  • Feature: Added commitMessage to outgoing APIs.

  • Feature: Improved UI interactions with the APIs.

3.30.22

Date:

Notable improvements are:

  • Feature: Data export and import.

  • Feature: Documentation improvements.

3.28.28

Date:

Notable improvements are:

  • Security: Dependency version update.

3.26.07

Date:

Notable improvements are:

  • Improvement: Now can separately configure from branches to consider, destination branches to consider, destination branches to ignore and destination branches to consider.

3.25.24

Date:

Notable improvements are:

  • Improvement: Allow editing configurations for Project/Repository readers.

  • Improvement: New query string parameters added.

3.25.03

Date:

Notable improvements are:

  • Improvement: Added a new filter for the repository slug on the project and global level. Now you can use a regular expression to filter repository slugs. (Java-style regular expression).

3.24.19

Date:

Notable improvements are:

  • Improvement: Added a new global setting Modification permit which allows Repository/Project writers to use REST APIs to manage configurations of their repository/project.

3.23.23

Date:

Notable improvements are:

  • Severe bug fixed for the migration from 2.5.3 to the next versions.

3.23.08

Date:

Notable improvements are:

  • Added support for additional Azure DevOps pipelines fields. More details are here.

  • UI improvement: hide unnecessary fields when selecting an authentication method.

3.22.28

Date:

Notable improvements are:

  • Added support of multiple Azure DevOps build pipeline parameters. See the guide for more information.

  • Bugfix: an empty event was sent during some PR events.

3.22.12

Date:

Notable improvements are:

  • Added support for Kerberos authentication.

3.21.20

Date:

Notable improvements are:

  • There is a global setting to allow/disallow projects to use this App.

  • There is a global setting to disable old Rest APIs.

3.20.22

Date:

Notable improvements are:

  • Added support to treat all rules separately. There are 2 system-level settings. Please read here.

  • Improved the empty state.

3.19.14

Date:

Notable improvements are:

  • Mask or hide sensitive information in the debug-level logs.

3.19.09

Date:

Notable improvements are:

  • Added functionality to be able to re-run the migration from an old version (2.4 or below). More details are in this guide.

JavaScript errors detected

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

If this problem persists, please contact our support.