Orangutan

A nice suggestion from one of potential Orangutan clients...

Carmen De Vito:

The next step would then be to decouple the relationship between LDAP and IM names. Maybe we can perform IM username lookups via a custom field or with the user’s email address.

• Store redmine user login in Orangutan::User as new member login [DONE];
• Use special function GetLogin to fetch Redmine user login when comparing (search for $user->GetJabberUserID) [DONE];
• Use special function (e.g. Orangutan::User::GetDisplayName) to display just login, first and last name or JID (use login@hostname if jabber field¹ is disabled) instead of login@hostname (search for $main::config->Get('jabber', 'hostname')) [DONE].

¹ New special field holding user’s Jabber ID is to be called jabber.

• Should check all occurances of GetUser() function and possibly replace with GetUserLogin() [DONE];
• When in requests username does not contain @hostname Orangutan adds hostname by itself - should assume that this is login (right?)! All such places marked with FIXME;
• Should also check all occurances of UserExists;
• Check all places where login is used (mostly in Orangutan::Query).

• Should check all occurances of GetUser() function and possibly replace with GetUserLogin() [DONE];
• When in requests username does not contain @hostname Orangutan adds hostname by itself - should assume that this is login (right?)! All such places marked with FIXME [DONE];
• Should also check all occurances of UserExists [DONE];
• Check all places where login is used (only Orangutan::Query left) [DONE];
• Fix all FIXMEs (this way I marked potential problems)...

P.S. Weird... But I could not update above note!..