If anyone wants i created a nodejs script to sync users username's to their displayname.

This can be run hourly or how ever you see fit. It requires read and write access to the mysql database, and read access to the config.xml file in the fisheye home folder.

https://github.com/ludjer/fisheye-user-mapping

Have a ugly work around but still saved thousands of hours for mapping bad user emails to each repo..
Jam it in the DB.

Work around for MySQL

INSERT IGNORE INTO cru_committer_user_mapping (cru_committer_name, cru_repository_name, cru_user_name)
SELECT
  users.commitauthor,
  repos.cru_content_root_rep,
  users.cru_user_name
FROM (SELECT DISTINCT
         cru_content_root_rep
       FROM cru_content_root) repos,
     (SELECT DISTINCT
         (cru_committer_name) AS commitauthor,
         cru_user_name
       FROM `cru_committer_user_mapping`) users

100+ repos and counting, setting up a tool on user / repo basis is not an option.

+1

I just had the same problem, it would help a lot with support for global mappings. I have about 200 mappings to add manually now, so not an impossible situation but annoying still.

It automatically maps the users who used exactly same name in commits and crucible account, but there's no option to create users automatically. I.e. you have to manually or with script to create all users or integrate to ldap. Also if an user has used multiple names in the commits across multiple repositories, there is no way to create a global mapping from all repositories, but you have to manually map the name per repository.

Additional features that would help are:

• Option to create automatically a user account for mapping
• Mapping of committer name from any repository to specific username in crucible (instead of per repository)

Isn't this feature available in Crucible? See https://confluence.atlassian.com/display/CRUCIBLE/Configuring+User+Managed+Mappings

1 MUST! I have to write a script for this because I have 180 repos and 100+ users..

Yes please.

+1 a must!

+1

Yes, please support it!

Same situation here but with 180 git repositories, some with 20 years of history.
The global mapping seems like a sensible solution to me
But if it is not feasible, my question is:
Is there a way to batch/automate this? with a script ordirectly adding them to the FE database?

That seems to be a trivial non-issue. In the case of shared logins for things such as cvs/svn there is no effective way to map which user did what, in the case of bad configuration for Git/Mercurial this is again an issue of end user support. In our use case we have approximately 18 repositories with history that spans across CVS, SVN, and Git for the majority of repositories (These repos started in CVS and migrated over time.) This is an absolute must as each user has 5+ committers that they need to link, across 18 repos, x12 active users (not counting those who have left the company sense.) That's a lot of mapping that could very easily be handled by creating a global map that is then overwritten by a local map (to the repository.)

The slight compication here is that global mappings could lead to clashes.

So if the same committer name was used in different repositories by different users, this would lead to a clash.