I disagree with the change proposed here. For the following reasons:

1. MantisBT can be replaced by a company name that is often much longer than the word MantisBT.
2. I would reserver the top space with the menus and buttons that are added by core or by plugins.
3. The look and feel is better the way it is. I don't see it as a good idea to have issue ids in the top bar for example.

I don't have a strong opinion about this so I don't mind the status quo, but I would like to hear your thoughts about the redundancy with the username in the "breadcrumb" div, which does not add any value IMO (we already have the username information in the top right, and I'm not convinced displaying the user's role is really useful).

we already have the username information in the top

Consider $g_show_realname == ON when discussing the issue

This is what we see in 1.3.x
<UserName> ( <RealName> - <AccessLevel> )

This is what we get in master after the changes to fix 0021681
<RealName> <AccessLevel> in breadcrumb div
<UserName> in navbar

and I'm not convinced displaying the user's role is really useful

I find it useful, when having private projects where the user have different access levels among them.

OK, I rest my case ;-)
Thanks for the feedback

Now I am the one who reopens, as I would like to hear your thoughts about the current implementation in 2.0 if $g_show_realname == ON.

Isn't this confusing?
<RealName> <AccessLevel> in breadcrumb div
<UserName> in navbar

Wouldn't it be better to have
<UserName> ( <RealName> ) <AccessLevel> in breadcrumb div?

Fine with me.

Opened 0021736 for 0021690:0054026