Loading...

XML

Word

Printable

Details

Type: Suggestion
Resolution: Unresolved
Fix Version/s: None
Component/s: Pull Request - Merge
Labels:
None

UIS:
2
Feedback Policy:

We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

Description

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?

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List

max-commit-summaries.png
22 kB
05/Sep/2019 9:15 PM

Issue Links

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...

mentioned in: Page Loading...; Page Loading...

(2 mentioned in)

Activity

People

Assignee:: Unassigned

Reporter:: SymphonyDevelopment

Votes:: 16 Vote for this issue

Watchers:: 24 Start watching this issue

Dates

Created:: 04/Jun/2013 1:59 PM

Updated:: 05/Apr/2024 3:05 AM