Differences to Data Center

This page lists everything that works differently in Smart Commits for Bitbucket Cloud compared to Smart Commits for Bitbucket Data Center, and which features are not supported yet.

Commits that contain an unsupported command are still processed. The unsupported command is ignored, and all other commands (e.g. transitions, comments) run normally.

Not yet supported

Feature	Data Center	Cloud	Comment
Time tracking (`#time`)	✅	❌	See the warning below.
Time tracking info in push response	✅ (original / spent / remaining)	❌	Depends on `#time`.
Comment visibility (`#comment @jira[Developer]`)	✅	❌	Comments are always visible to everyone who can see the issue.
Review approval handling (`#keep` / `#unapprove`, Keep- and Unapprove-Strategy)	✅	❌	Approvals are not changed by the app.
Push response (results printed in the `git push` output, severity setting)	✅	❌	Bitbucket Cloud does not offer a synchronous hook response. Actions run after the push.

Time tracking (#time) is currently not supported in Bitbucket Cloud.
Because all Jira actions run under the account of the Jira connection (see "Author of Jira changes" below), work logs would not be recorded under the developer who made the commit. Since that would make your time tracking inaccurate, we have disabled this feature for now.
We are looking into ways to bring it back in a reliable way. If time tracking via Smart Commits is important to you, please let us know. Your feedback helps us set priorities.

Behaves differently

Topic	Data Center	Cloud
Jira connection	All Jira actions use the primary application link.	Jira actions use the Jira connections configured in the app settings. Multiple connections are possible, and the workspace, project and repository levels control which ones are used.
Author of Jira changes (comments, transitions, assignee, …)	The commit author	The account of the Jira connection This applies to all actions in Jira, not the developer who made the commit.
Author of Bitbucket changes (comments, tasks)	The commit author	The Smart Commits app
Pull requests created with `#pull`	Created as the commit author	Created by the Smart Commits app
Date of a comment	Date of the push	Date of the push
`#assignee`	`#assignee=<username>`	`#assignee=<display name or email>`
`#fixVersion`	`#fixVersion`	`#fixVersion` and `#fixedVersion` are both accepted
Jira comment header	`$url`, `$repo`, `$hash`	Additionally `$short-hash`
Configuration	Project and repository hooks	App settings on workspace, project and repository level
`#reviewer @user`	Bitbucket username	Bitbucket Cloud user (see the syntax section)

Things to keep in mind when migrating

Double execution: If your workspace also uses Jira's built-in Smart Commits, commands like #comment or transitions may be executed twice.
Time bookings: Existing commit messages with #time keep working, but the time entry is ignored. Use Jira's own worklog until time tracking is supported.
Connection setup: Before the first push, a Jira connection must be created at workspace level and enabled for the project or repository.