FishEye displays an incorrect committer for a user with an underscore in its username

Summary

The committer information is not displayed correctly when accessing a changeset in case the user contains an underscore in its username.

Steps to Reproduce

The steps below have been tested with a Git repository, but they may apply to other repository types.

1. Create a user in FishEye with yut as Username, Yut as Display name and yut@fisheye.com as Email
2. Create a user in FishEye with y_t as Username, Y_t as Display name and y_t@fisheye.com as Email
3. These are the users in FishEye after the steps above
4. In a Git repository, set the Git configuration option for user.name and user.email to match the user with the underscore so that the Git config -l command returns:

   • git config -l
     user.name=Y_t
     user.email=y_t@fisheye.com
     

5. Commit and push to the Git repository. The Git log command returns Y_t as Author:

   • git log <commit_hash>
     commit ae59dba0943811fdbcbd76ab0f2e1938e87b9c1d
     Author: Y_t <y_t@fisheye.com>
     Date:   Tue Feb 9 11:30:17 2016 +1100
     

6. Locate the commit in FishEye

Expected Results

The Y_t display name, matching the y_t user, is displayed as committer.

Actual Results

The Yut display name, matching the yut user, is displayed as committer.

When clicking on the user displayed, the page containing the details of the yut user (without the underscore) is loaded (note the <FishEye url>/user/yut in the title bar), and the page shows the "This user has not yet committed." message:

Notes

The user creation sequence (yut - user without the underscore before y_t - user with the underscore) is critical. If the users are created in the reversed sequence, then the problem does not occur.

Workaround

Delete the user shown instead of the expected one, yut in this example, and recreate it.
The correct username is displayed after the user yut is deleted, and recreated: