Uploaded image for project: 'FishEye'
  1. FishEye
  2. FE-4492

Git Commit will display username <email> from Git on the JIRA source tab

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • N/A
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      It seems that when a user makes a Git commit, the username will be displayed as the username in Git together with <email in Git> on the Activity Stream and Source Tab without respecting the Committer Mappings in Fisheye or the Application Link Connection.

      For example, the username on my Git VCS is

      • username: admin
      • email: immanuelsiagian@mail.com

      Generally, if you are using SVN or Perforce for the source control system, only username identified in JIRA will be displayed.

      However, for Git commit only, it will display both username and email from Git.

      It would be great if similar behaviour for SVN is inherited similar to Git.

        1. activitystream.png
          activitystream.png
          8 kB
        2. sourcetab.png
          sourcetab.png
          8 kB

            [FE-4492] Git Commit will display username <email> from Git on the JIRA source tab

            Atlassian Update – 5 October 2018

            Hi everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Timed Out.

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details.

            We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Regards
            Marek Parfianowicz
            Fisheye/Crucible TL

            Marek Parfianowicz added a comment - Atlassian Update – 5 October 2018 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Timed Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Regards Marek Parfianowicz Fisheye/Crucible TL

            beauco added a comment -

            This is an issue for my project to... The result is that using GIT makes Jira look crappy having a lot of unknown users at the source tab and timeline.

            https://support.atlassian.com/browse/JSP-162966

            beauco added a comment - This is an issue for my project to... The result is that using GIT makes Jira look crappy having a lot of unknown users at the source tab and timeline. https://support.atlassian.com/browse/JSP-162966

            To try to add a little bit of information on this.

            It could be a problem that has been introduced by the way FishEye has now categorised users.

            Previously this used to be just username and that logic also identified how many licences were being taken up by FishEye when you re-cloned and re-indexed a Repo.

            Now this has been change so that a user is considered unique based upon their username and email address combination. May be a reason for the problem?

            Supporting links:

            http://confluence.atlassian.com/display/FISHKB/Git+or+Hg+Repository+exceeds+number+of+allowed+Committers;jsessionid=AEB2DAEB8A6A64BCCFA0BBDC406C33FD
            https://jira.atlassian.com/browse/FE-2496

            James

            James Heggs added a comment - To try to add a little bit of information on this. It could be a problem that has been introduced by the way FishEye has now categorised users. Previously this used to be just username and that logic also identified how many licences were being taken up by FishEye when you re-cloned and re-indexed a Repo. Now this has been change so that a user is considered unique based upon their username and email address combination. May be a reason for the problem? Supporting links: http://confluence.atlassian.com/display/FISHKB/Git+or+Hg+Repository+exceeds+number+of+allowed+Committers;jsessionid=AEB2DAEB8A6A64BCCFA0BBDC406C33FD https://jira.atlassian.com/browse/FE-2496 James

              Unassigned Unassigned
              isiagian Immanuel Siagian (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: