View Issue Details

IDProjectCategoryView StatusLast Update
0024139mantisbtuipublic2018-04-13 11:30
ReporterstainlessstillAssigned To 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
Product Version2.12.0 
Target VersionFixed in Version 
Summary0024139: $g_show_realname for making usernames private
Description

In version 2.12.0 $g_show_realname doesn't work as it used to in previous versions.
We use realnames for not exposing usernames to public. That made sense since users could choose to introduce themselves in a way they wished to while being able to edit their personal (public) info freely without being limited to their unmodifiable username.
I've read all the stuff about the uniqueness concerning the 2.12 release but it has brought changes that made such info no more adjustable.
If there is a way to revert or make some special config settings to leave usernames (logins) private and expose only real names to public?
PS also having realnames as bubbles (tooltips) is not intuitive for members who are not developers and only have used the system for project management and are not experienced to look for something (real names) that had been clear and explicit before (without hovering a mouse).

TagsNo tags attached.

Relationships

related to 0024087 closedatrol $g_show_realname problem on 2.12.0 
related to 0024069 closedvboctor Show realname not working 

Activities

stainlessstill

stainlessstill

2018-03-19 19:14

reporter   ~0059240

If real names behaviour could be reverted (in config) to old-style handling and it conflicted with @mention or something, you could cut off automatically the whole @mention functionality and all the stuff that conflicts with it. Not everyone uses @mention. Supposedly.

stainlessstill

stainlessstill

2018-03-19 20:06

reporter   ~0059241

Also some users (for example outsourced contractors) historically have usernames as their emails. So showing usernames all the time is inappropriate for our tasks. It would be quite reasonable for us to display real names by default while usernames as tooltips if it has to be so (or better not at all).

For the projects that have no strict requirements for usernames this change ruins the ui and exposes what shouldn't be exposed.

stainlessstill

stainlessstill

2018-03-19 20:20

reporter   ~0059242

There could be javascript solutions for @mentions using real names. For example suggestions may pop up triggered by @ sign. I understand that it supposedly entails big code changes and editor area rework. That's all for now. :)

atrol

atrol

2018-03-20 03:40

developer   ~0059243

We use realnames for not exposing usernames to public.

I am not aware this was ever possible.
You can click on the real name in activities to see the username on view_user_page.php.

stainlessstill

stainlessstill

2018-03-20 04:48

reporter   ~0059244

Real name speaks for itself than a username. With $g_show_realname we make usernames not that obvious as they are no that informative and inconvenient for comprehension.

vboctor

vboctor

2018-03-21 03:06

manager   ~0059253

It is common practice to always show usernames. For example:

  • Github uses usernames
  • PHPBB uses usernames
  • Twitter shows usernames + real name next to tweets

Hiding usernames was not ever a goal and was always discoverable.

stainlessstill

stainlessstill

2018-03-21 03:58

reporter   ~0059258

ok. When you know the rules, you follow them. We know that some web-stuff requires usernames. But here the rules has changed. And that changed the way the info is displayed in comparison to how it used to be. By making private I'm not speaking about hiding data rather than I'm speaking about exposing relevant data like real names. E-mails (some of our users has it as usernames) are irrelevant in this case while real names from profiles are relevant. For example, emails like usernames not only look ugly, they don't even work for comprehension and personalisation.

atrol

atrol

2018-03-27 17:38

developer   ~0059327

Proposal from 0024087:0059267

What about replacing $g_show_realname by something like $g_display_user_format ?

#define ( 'USERNAME', 0 );
#define ( 'REALNAME', 1 );
#define ( 'USERNAME_REALNAME', 2 );
#define ( 'REALNAME_USERNAME', 3 );

$g_display_user_format = USERNAME;
  • USERNAME display user name, no real name
  • REALNAME display real name, display user name if real name is not set or access is not allowed
  • USERNAME_REALNAME display user name, real name as bubble or in brackets, if access is allowed
  • REALNAME_USERNAME display real name if set and access is allowed, display user name as bubble or in brackets. If not set or not allowed, display user name.
Ruzhelovich Vladimir

Ruzhelovich Vladimir

2018-04-05 01:22

reporter   ~0059434

"stainlessstill" +1

I have the same problem

Ruzhelovich Vladimir

Ruzhelovich Vladimir

2018-04-05 01:33

reporter   ~0059435

0024139:0059327

If this format is displayed on the form instead of USERNAME, then I agree it. This will be solution the problem

stainlessstill

stainlessstill

2018-04-05 04:49

reporter   ~0059440

Last edited: 2018-04-05 05:33

View 2 revisions

0024139:0059327

What about replacing $g_show_realname by something like $g_display_user_format ?

If I get that right, that will solve the problem. If old mantisbt installations had an option to manage new username display rule, that would be a great lifesaver.
Thanks for not ditching it and for your supportive attitude. :)

Edit [dregad]: markdown

sananas

sananas

2018-04-13 11:30

reporter   ~0059566

"stainlessstill" +1

I have the same problem

We work with physical person and not virtual user.
Showing usernames like "CA1245" or "ME9645" all the time is inappropriate for our tasks.

Then i modifed function prepare_user_name in prepare_api.php with using show_realname : cf JPG

but, If it's possible to add an option to manage how we can show username that will be great.

thanks



prepare_user_name.JPG (105,842 bytes)
prepare_user_name.JPG (105,842 bytes)

Issue History

Date Modified Username Field Change
2018-03-19 19:06 stainlessstill New Issue
2018-03-19 19:14 stainlessstill Note Added: 0059240
2018-03-19 20:06 stainlessstill Note Added: 0059241
2018-03-19 20:20 stainlessstill Note Added: 0059242
2018-03-20 03:40 atrol Note Added: 0059243
2018-03-20 03:42 atrol Relationship added related to 0024087
2018-03-20 03:43 atrol Relationship added related to 0024069
2018-03-20 04:48 stainlessstill Note Added: 0059244
2018-03-21 03:06 vboctor Note Added: 0059253
2018-03-21 03:58 stainlessstill Note Added: 0059258
2018-03-27 17:38 atrol Note Added: 0059327
2018-04-05 01:22 Ruzhelovich Vladimir Note Added: 0059434
2018-04-05 01:33 Ruzhelovich Vladimir Note Added: 0059435
2018-04-05 04:49 stainlessstill Note Added: 0059440
2018-04-05 05:33 dregad Note Edited: 0059440 View Revisions
2018-04-13 11:30 sananas File Added: prepare_user_name.JPG
2018-04-13 11:30 sananas Note Added: 0059566