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

Show both author and committer information on Bitbucket Server UI

    • Icon: Suggestion Suggestion
    • Resolution: Done
    • 6.9.0
    • Git Hosting
    • None
    • 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.

      Atlassian update: 13-dec-2019

      Thanks for your feedback on this suggestion. Bitbucket Server and Data Center 6.9 onwards if committer and author were different, both of their avatars will be displayed on the commit. Hovering on the avatar you will be able to see the committed/authored date.

      Original description: 

      Problem Definition

      At the moment Bitbucket Server only shows the author in the UI.

      However, Git logs both author and committer. If you make a change and commit, you are both the author and committer. But if a developer cherry-picks a commit, the author is retained and the cherry-picking user will be recorded the committer. (The same is true for rebasing, or amending commits; by default authorship is retained and only the committer is updated.)

      Suggested Solution

      Show both the author and the committer in the UI when they are different.

      Workaround

      There is no current workaround for seeing this information on Bitbucket Server.

            [BSERV-8868] Show both author and committer information on Bitbucket Server UI

            Imran Khan added a comment -

            Hi everyone, 

            Thanks for your feedback on this suggestion. Bitbucket Server and Data Center 6.9 onwards if committer and author were different, both of their avatars will be displayed on the commit. Hovering on the avatar you will be able to see the committed/authored date.

            Cheers,
            Imran Khan
            Product Manager - Bitbucket Server

            Imran Khan added a comment - Hi everyone,  Thanks for your feedback on this suggestion. Bitbucket Server and Data Center 6.9 onwards if committer and author were different, both of their avatars will be displayed on the commit. Hovering on the avatar you will be able to see the committed/authored date. Cheers, Imran Khan Product Manager - Bitbucket Server

            Catalin Gheorghe added a comment - - edited

            Hope this gets addressed, as it is at least incomplete, if not misleading. Especially if the cherry-picks are done without `-x`

            Catalin Gheorghe added a comment - - edited Hope this gets addressed, as it is at least incomplete, if not misleading. Especially if the cherry-picks are done without `-x`

            I can only agree and add to the importance of this issue: Using Squash+Rebase without having both information visible is absolutely broken right now. And to add insult to injury when squashing with the Bitbucket Server web UI it even writes the one who pressed the squash button in both the committer and author field.

            This completely annihilates my ability to use this feature given that i don't want to completely wreck accountability.

            Meik Tranel added a comment - I can only agree and add to the importance of this issue: Using Squash+Rebase without having both information visible is absolutely broken right now. And to add insult to injury when squashing with the Bitbucket Server web UI it even writes the one who pressed the squash button in both the committer and author field. This completely annihilates my ability to use this feature given that i don't want to completely wreck accountability.

            Ross added a comment -

            Agreed on this issue, or at least the ability to show committer instead of author. We are using git in a non-distributed way and only care about who the committer is, which by extension is who did the push because of the Verify Committer hook. Author is nice information to have to see who may have wrote the code but committer is ultimately the person responsible for the change (since they deemed the changes worthy of push).

            Ross added a comment - Agreed on this issue, or at least the ability to show committer instead of author. We are using git in a non-distributed way and only care about who the committer is, which by extension is who did the push because of the Verify Committer hook. Author is nice information to have to see who may have wrote the code but committer is ultimately the person responsible for the change (since they deemed the changes worthy of push).

            Agreed, this would be very useful.

            Shane Wignall added a comment - Agreed, this would be very useful.

            As of Bitbucket Server 4.6.2 only the Author is shown.
            I agree that it would be useful to have both Author and Committer information shown.

            Steven Whitman added a comment - As of Bitbucket Server 4.6.2 only the Author is shown. I agree that it would be useful to have both Author and Committer information shown.

            Robert Obuch added a comment - - edited

            As a heavily regulated enterprise, there is value for us in knowing both author and committer and having access to both on the Web UI and programmatically via the API.

            In your description, you mention Bitbucket Server only shows the committer but I think this needs to be verified because I think it actually shows author.

            Robert Obuch added a comment - - edited As a heavily regulated enterprise, there is value for us in knowing both author and committer and having access to both on the Web UI and programmatically via the API. In your description, you mention Bitbucket Server only shows the committer but I think this needs to be verified because I think it actually shows author.

              Unassigned Unassigned
              tbomfim ThiagoBomfim (Inactive)
              Votes:
              58 Vote for this issue
              Watchers:
              34 Start watching this issue

                Created:
                Updated:
                Resolved: