- show users with their real name or not

and make real names unique

Real names are not unique.

It doens't matter if real names are unique, but there are some old Tickets, which are not really important for the Major use case

As you are not asking for unique real names, do you are asking for something that is not covered in 0024432 ?

Please build $g_show_realname = ON back like it was until <= 2.11.1 - the change in 2.12 is the blocker.

The non plus Ultra solution is your recommendation 0024139:0059327 until 0024139:0059327, the blocker must be made gone

Resolved as duplicate of 0024139 as tracking two issues for the same problem does not add value.

Dear atrol,

I do not agree with setting this ID as resolved as duplicate of 0024139, because 0024139 is a minor bug - 0024432
describes an update blocker and asks for a return to the basic mantisbt function used until 2.11.1 in 2018 - even 0024139 is eventually implemented.
Users of the $ g_show_realname = ON function are actually blocked in 2.11.1 an are not able to perform their upgrades to> = 2.12, 2.14, and so on!

This ticket describes a structurally conceptual error in the implementation of loss of required functions in Display the Realname in masks and statusmails, while # 24139 describes a general improvement.

Best regards,
Karl!

@mahindra I don't understand what you want to tell.
The user who reported 0024139 requested to revert to the 2.11.1 behavior and you request the same.
Both of you requested that usernames are not exposed to public, but that was never the intention of $g_show_realname = ON, see also my comment 0024139:0059811

0024139:0059829 Thank you jensberke has written a summary

https://mantisbt.org/bugs/view.php?id=24186.
[security] CVE-2018-1000162: XSS vulnerability in Parsedown library (dregad)
Resolved in 2.12.1

Please built the visibility of Realnames back like 2.11.1 or make a security version 2.11.1.1

Have a look at this the ID is visable with Realname=ON
This is like Realname off - and does not meet with usability or security guidlines if you have to do a mousover to see the realname while the user-ID is in front and visible

userid visible realname on.png (5,959 bytes)   

userid visible realname on.png (5,959 bytes)   

userid visible realname on (2).png (2,993 bytes)   

userid visible realname on (2).png (2,993 bytes)   

The reason for this misdirection is - how to add users monitoring a ticket:
<<<The real solution to add users to a ticket is a drop down list like 0012557 >>>
If Realname is on - it shows realnames like Mantis before 2.12 in every User field
If Realname is off - it Shows the User ID

Similar to the filter selection for user
Simple and clean
Please go in this direction and delete 0023375 go back to the previous solution in visualization Realnames up to version 2.11.1 this was clean and improve adding a user to a ticket with a drop-down list

You are moving in circle with 0024436, 0024435 and all the other IDs currently

In order to see this topic you have to work in the corresponding representation - only user ID or only real name instead of user ID - then it is easy to understand

0024436 on hold please, 0023375, 0024435, 0024378, 0024087

Thanks again atrol
That's why mantis is the best bugtracker - the people behind the project and the opportunity to talk to each other.

When we get 0024139:0059859 in release 2.15, we have a solution, a compromise and a base for further development.

@vboctor please wave that through!

https://mantisbt.org/bugs/view.php?id=24186.
[security] CVE-2018-1000162: XSS vulnerability in Parsedown library (dregad)
Resolved in 2.12.1

Please built the visibility of Realnames back like 2.11.1 or make a security version 2.11.1.1 we are sticking here until we see Realnames!
or
better do solution from @atrol 0024139:0059929 in next release 2.15, please!

The concept can be improved like 0024139:0059566, parallel to the releases, if needed or someone has time...

Resolved in 2.15.0 after merge of PR https://github.com/mantisbt/mantisbt/pull/1351

This is a theme from the versatility of Mantis that makes it so good, on the other hand, to understand quite abstractly - especially if you do not need some function yourself.

From an application point of view, I can only recommend user selection - where possible outside of the text (reminder, combo, etc.) to make and ask for display conversions - straight, when it comes to naming - straight to lead.

Thanks again - I will report if I get topics because of the better user-ID view, which is better hidden in ours, where possible.

Ticket can be closed. Thank you very much!