PR Author listed as commit author instead of the User that merged

Issue #13960 closed
Ronald Chia
staff created an issue


When User A makes a pull request and User B merges it, BitBucket uses User A as the commit author for the merge commit which supposed to be User B who is the one that performed merged. This affects the actions triggered in JIRA by the smart commit message which shows the merge are done by User A instead of User B

Sample Image MergePR.PNG

Comments (7)

  1. Abhin Chhabra

    This is related to a relatively recent change to Bitbucket that sets the merge commit's "author" field based on the user who created the pull request and and the merge commit's "committer" based on the user who hit the merge button. This is the right thing to do.

    But, historically, Bitbucket hasn't differentiated between the author and committer fields. This means that the UI uses them interchangeably. This is far from ideal. I would like to see Bitbucket displaying both these fields for commits.

    I hadn't anticipated the JIRA integration to break because of this, but in hindsight I should have. I expect the fix to be relatively easy on the easy_connect side, so I'll ping @Megan Cook and see if this is something they could add to their backlog.

  2. Alastair Wilkes staff

    Given the low interest in this bug since it was raised, and since it is an edge case, I am closing this issue as "won't fix" to reflect that we won't be able to address this in the near future.

  3. Kris Meister

    @alwilkes This issue also appears, when an Reviewer uses smart commit tags:

    BUG-1234 #ready-for-qa #comment As the PR Merger comments should attribute to me.

    Unfortunately doing this has all attribution (moving the ticket and comment on the ticket, in jira) to the original PR creator.

    This causes confusion on our TEAM as that person will be asked questions about comments they did not make.

    Created: 16718 to track the smart commit message portion.

  4. Log in to comment