I note that a corrective version (4.1.1) of the software has been released. As this quickly follows of from the initial 4.1 release 2 days ago then I note that 4 tickets (Track database, 1259-62) have been treated for the 4.1.1 release. The following also need addressing:
- confusion of user and username columns resulting in
- failure of the Import feature of Resources
- search and lookup in a number of drop-down lists display the login name rather than the more meaningful 'full' name
- Activities Prices seem to be diconnected
failure of the Import feature of Resources
Could you describe more explicitely this issue ?
search and lookup in a number of drop-down lists display the login name rather than the more meaningful 'full' name
It is designed this way.
Some fields list users (creator), some list contacts (requestor), some list resources (responsible).
Users list displays the login name.
Activities Prices seem to be diconnected
Could you describe more explicitely this issue ?
You may think that the use of 'username' is a design feature but such is inconsistently used. Consider the Activity form - issuer uses the 'username' and immediately under this field, the requestor uses the 'fullname' and yet both represent the same namespace.
Given that large organisations (mine is 14,000+) tie their Active Directory to their payroll system then the unique identifier throughout AD is the employee number. The employee number would be the link through LDAP not some arbitrarily assigned sequence of characters dreamt up by the Project team.
Furthermore, The following ticket, stated verbatim, raised in a real world Public Safety institution against a globally recognised software company highlights the 'pain' it causes to the business when using 'usernames'
==Business Justification== Currently users are spending excessive time to work out who has created, taken action and entered comments into cases. This is due to the User ID field only displaying the payroll only, thus the user must look up each payroll every time they wish to ascertain who entered the case comment.
Please reconsider your "design"
I still concider it is a design feature : users don't mandatory have full name. They must have one only if they also are Resource or Contact.
But I agree it could ease readability to retrieve the full name of user when it exists.
But then, for users without a full name, user name must still be displayed, and there should be some difference between "user name" and "fullname" display.
I'll think about it.
Ticket #1288 recorded.
Instead of "full name", this field could be named "display name" and be filled in with the user name by default...
Ticket #1288 has been treated.
User fullName, corresponding to Resource name is displayed by default.
If not set, then user name is displayed, followed by #.
I'll have a look at your (good !) proposition in renaming fields...
Please give this some careful consideration.
The rule of thumb is never to display the username (login name) if at all possible as it exposes half of the user's account credentials. All fields that presents a person's name (including entity names) works best when such name is immediately recognised and is discernible from other names.
Using a 'display' name is useful for 'sites' where there is little consequence or interaction between the subscribers and casual users - for example, this forum site. In other sites where there is a very high degree of interconnection (eg. Facebook, LinkedIn...) then real world common names are used. Of course there are always those who use pseudonyms to remain anonymous.
For Project Management software then real world names are applicable as there are no anonymous users - each person is either Responsible, Accountable, Consulted or Informed and they will expect to be Paid!
If Projeqtor is to become a credible tool in the Enterprise then lift its 'professional' appearance then drop the use of 'display' name. Better not to give my Directors the 'feel' that Projeqtor is like 99% of blogging and forum sites that populate the internet. For those who want to remain anonymous then Fred Nerk as a fullname would suffice.
Hi,
I understand your point of view.
My idea is just to make things clear.
IMO Display Name is not a pseudo but show it is the name that will be displayed (in list).
Of course it should be real name.
What is important is that ProjeQtOr is radically different from forum or social sites : users don't choose there display name. It is an administrator who defines resource names ...
And in an Enterprise, ProjeQtOr should be connected to LDAP. Then, resource name directly comes from LDAP.
But you're right, maybe "real name" could be better than "display name".