Merge commit message produces duplicate time entries

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Unresolved
    • None
    • Component/s: Pull Request - Merge
    • None
    • 1
    • 7

      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
          max-commit-summaries.png
          22 kB

            Assignee:
            Unassigned
            Reporter:
            SymphonyDevelopment
            Votes:
            16 Vote for this issue
            Watchers:
            24 Start watching this issue

              Created:
              Updated: