Good idea!! I implemented it locally straight away.

If you want it quickly, open core/string_api.php

Go to line 404. After the line '$t_status= ... ', insert the code between the "###":

##########################################
$t_handler_id = bug_get_field( $p_bug_id, 'handler_id' );
if (user_exists($t_handler_id))
{
$t_handler_name = string_attribute( user_get_name( $t_handler_id ) );
}
else if ($t_handler_id == 0)
{
$t_handler_name = lang_get('my_view_title_unassigned');
}
########################################

And change lines 406-408 that look like this:
if ( $p_detail_info ) {
$t_link .= ' title="[' . $t_status . '] ' . $t_summary . '"';
}

into this:

if ( $p_detail_info ) {
$t_link .= ' title="[' . $t_status . '] '. " $t_handler_name - " . $t_summary . '"';
}

Also, as far as "hover" in My View, maybe it makes more sense to just use hover to show elements that you can't already see in My View... aka the issue summary is already shown in My View, and it also shows when you hover...so maybe replace that description with "assigned to" and a few other elements that are not shown (assigned to, etc).

Even geekier: Allow users to choose in their profile what is shown in a "My View/hover" situation.

Also, possibly make "hover" trigger over the entire row, not just the issue number.

I'll stop now... ;o) jj

Excellent thought. It should show what's invisible, not what's already there.
To that effect, many more elements could have a 'hover' function as far as I am concerned. It looks really good.

On a more serious note, allowing the user to choose what to hover and what not; I just read an article in the Scientific American that states that more choice does not make people happier... ;-)