Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-3529

Merge commit message produces duplicate time entries

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Pull Request - Merge
    • None
    • 1
    • 7
    • 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.

      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?

        1. max-commit-summaries.png
          22 kB
          Bryan Turner

              Unassigned Unassigned
              1b4fba9d89f2 SymphonyDevelopment
              Votes:
              16 Vote for this issue
              Watchers:
              24 Start watching this issue

                Created:
                Updated: