-
Bug
-
Resolution: Fixed
-
Medium
-
github + jira on demand
-
1
-
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:
- Create remote branch: bugfix/ASD-123
- Push a new commit to the new branch with commit message: ASD-123 #comment Fixed multiple parses #time 1h'
- Switch to main branch and make a new commit.
- Push the commit to remote main branch.
- Rebase branch bugfix/ASD-123 onto main
- Push --force onto origin bugfix/ASD-123
- Verify Jira issue ASD-123 which now contain 2 comment and 2h time
- Create a pull request to merge ASD-123 to main branch with squash merge option.
- Verify Jira issue ASD-123 which now contain 3 comment and 3h time
Expected behaviour:
Only 1h should be logged against ASD-123
- relates to
-
JSWCLOUD-14210 Smart commits are processed more than once.
- Closed
-
JSWCLOUD-17790 Merge commit messages result in duplicate entries in Jira when using Smart Commits.
- Closed
-
BSERV-3529 Merge commit message produces duplicate time entries
- Gathering Interest