Skip to main content
Skip table of contents

Version 3.0.0

Release Notes

Key T Status Summary Description Affected Versions Fix Versions
SCFB-6 Bug Resolved The keyword @stash is used to create a Pull-Request comment

The plugin has been developed for Stash. Thats the reason, why magic keywords in the commit messages are based on the name @stash. Since the renaming to Bitbucket, the magic comments needs to be renamed also. Both keywords should be supported. Since the version 3.0.0 in addition also @bb is possible to create comments

1.0.0, 2.0.0, 2.1.0, 1.1.0, 1.2.0, 2.2.0, 2.3.0 3.0.0
SCFB-19 New Feature Resolved Report Remaining effort

With this extension it is possible to enable a reporting regarding the time tracking. If a user add a new worklog he will get a summary of the time tracking information of the issue.

Example commit message

#Log time
TEST-1 #time 2w

Example response message

SCFB-22 New Feature Resolved Set estimated Effort

A new smart action has been introduced. With this smart commit extension for Jira, it is possible to set the estimated remaining effort for an issue.

//Set the remaining effort of the issue TEST-1
TEST-1 #remaining 1w1d1h


SCFB-33 Improvement Resolved Data Center compatibility

The new addon has successfully passed the Data Center approval process. Now the addon is listed as fully compatible with Bitbucket Datacenter instances.

SCFB-34 New Feature Resolved Task creation support

A new smart action has been introduced. With this smart commit extension, it is possible to create tasks for pull requests.

//Add a task to existing pull request
#task my first task
#task my second task


SCFB-35 Improvement Resolved Use Bitbucket default logging mechanism

The logging in the configuration page has been removed. Instead use a more detailed logging to the bitbucket.log in the home directory of Bitbucket. This logging needs to be enabled (see FAQ - Enable detailed logging)

SCFB-36 Improvement Resolved Performance improvements

Several improvements has been done.

Major improvement is the concurrency behaviour:

  • If the push response is disabled, all actions will be executed as a background process and the push returns directly, but without message.
  • If the push response is enabled, the behaviour is like in previous versions. The push will response messages, based on the configured response level (info|warning|error)
  • Time-out Even if the push response is enabled, the smart commit actions can run in the background. A time-out can be configured for this. As long as this timeout has not expired, the actions are executed normally and the executed actions generate the usual messages as push response. If there are still actions to be executed after the timeout, these actions are executed in the background and the "push" returns directly. (and prints only the already executed actions)
SCFB-37 New Feature Resolved Project and Repository configuration

The add-on configuration has been moved to the post hooks area. Now it is possible to configure the add-on on Bitbucket project level. The settings can be inherited to repositories.

SCFB-38 New Feature Resolved Possibility to disable actions exclusive

It is possible to disable and enable each smart commit action exclusive. So you can decide which actions you would like to use and which actions you would like to ignore.

Jira actions

Bitbucket actions

2.0.0, 2.1.0, 2.2.0, 2.2.1, 2.3.0 3.0.0
SCFB-39 Bug Resolved A reviewer action was not possible together with a pull request creation

In some situations it was not possible to create a pull request and add a reviewer in the same commit message.


#pull master #reviewer @tester
2.0.0, 2.1.0, 2.2.0, 2.2.1, 2.3.0 3.0.0

Known Bugs

Key T Status Summary Description Affected Versions Fix Versions

JavaScript errors detected

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

If this problem persists, please contact our support.