-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
2
-
Stash will add all previous commit messages into a merge commit message, this results in duplicate time entries in JIRA when using FishEye Smart Commits.
Steps to reproduce:
- Create a branch and commit a change with "KEY-123 #time 10m"
- Create a pull request for the branch and merge it
- The merge commit that Stash creates will contain "KEY-123 #time 10m" again
- 20 minutes will be logged against issue KEY-123
Expected behaviour:
- Only 10 minutes should be logged against KEY-123
Suggested fix:
- Remove all previous commit message from the merge commit message - isn't this what `git log` is for?
- is related to
-
JSWCLOUD-14140 Merge commit messages result in duplicate time entries in Jira when using Smart Commits
- Closed
-
JSWSERVER-14140 Merge commit messages result in duplicate time entries in JIRA when using Smart Commits.
- Closed
- relates to
-
BSERV-2826 A user can edit the commit message when merging a pull request
- Closed
-
BSERV-6980 Add option for not including individual commit messages in pull request merge commit messages
- Closed
-
FSH-16246 Loading...