|Title||Users with spaces produce confusing errors|
|Assigned user||Richard Brooksby|
|Description||A Bugzilla or TeamTrack user name containing spaces causes confusing errors to be produced by the P4DTI, especially when it doesn't correspond to a Perforce user, and perhaps even when it does.|
|Analysis||I believe the P4DTI is trying to enter the name with spaces in the "Assigned_to" field in Perforce, but this is illegal, because the field only accepts a single word. It's a bug that we produce such an obscure error in this case. Perhaps we should accept names with spaces anyway. E-mail addresses can legally contain spaces (which aren't significant), although it's rare. RB 2001-04-10|
GDR 2001-07-17: We should report this as an error or at least a warning when we check addresses at startup.
GDR 2001-10-02: This can happen in TeamTrack as well; see .
|Evidence||Look at  <|
Perforce support CALL#178704.
|Created by||Richard Brooksby|
|Created on||2001-04-10 13:27:56|
|Last modified by||Gareth Rees|
|Last modified on||2002-01-29 14:49:24|
|History||2001-04-10 RB Created based on support incident.|
2001-10-02 GDR Noted that this can happen in TeamTrack.
|26195||closed||2002-01-29 15:20:24||Gareth Rees||Updated test data to include user names with spaces in (regression test for job000289).
User translators apply the keyword translator for unknown users, in case they have spaces or other forbidden characters.