Merge commit messages result in duplicate time entries in Jira when using Smart Commits

Commit messages with #time create multiple time logs on the Jira issue if they also appear in merge commit messages.

Similar issue filed against Bitbucket Server: STASH-3529

Date: 11-Nov-2020
Issue re-appearing on Bitbucket cloud.
Steps to reproduce:

1. Create remote branch: bugfix/ASD-123
2. Push a new commit to the new branch with commit message: ASD-123 #comment Fixed multiple parses #time 1h'
3. Switch to main branch and make a new commit.
4. Push the commit to remote main branch.
5. Rebase branch bugfix/ASD-123 onto main
6. Push --force onto origin bugfix/ASD-123
7. Verify Jira issue ASD-123 which now contain 2 comment and 2h time
8. Create a pull request to merge ASD-123 to main branch with squash merge option.
9. Verify Jira issue ASD-123 which now contain 3 comment and 3h time

Expected behaviour:
Only 1h should be logged against ASD-123