305174 - Confirm Match should list the bug number and description

Status: NEW

(Bugzilla :: Creating/Changing Bugs, defect)

Description

[timeless]

steps:
1. visit a bug 
2. cc @mozilla.org 
3. click submit
4. go out to lunch
5. return

actual results: 
Confirm Match  
    

One or more of the names/email addresses you entered into fields on the 
previous page produced results which require confirmation. Please carefully 
examine the matches below, selecting users from the lists if necessary, or go 
back to the previous page to revise the names you entered. 


--------------------------------------------------------------------------------
 
CC:  @mozilla.org matched: 

Questions:
1. what bug did you just change?
2. if you're using ie, will ie eat your comment if you try to use back to find 
out?

Comment 1

[Frédéric Buclin]

What should be displayed when changing several bugs at once? And when using editcomponents.cgi or request.cgi?

Comment 2

[timeless]

> changing several bugs at once?

list the affected rows as they were shown in buglist?tweak=1 (see bonus points below)

> editcomponents.cgi

list the affected component bits (see bonus points below)

> request.cgi

list the filter bits. bonus points for using request.cgi's normal output and simply replacing the textfield w/ the chooser.

I've seen your several bugs at once question, so i'll raise you one:
what happens if actor=[e-mail] (member of security, webtools) and strict isolation is set cc's timeless (inconclusive) and selects timeless@gmail (webtools, not security) for two bugs (one security, one webtools).

Comment 3

[Guy Pyrzak]

Ok, so this isnt a UE question at all. And if it is I'll answer it. Not showing what bug you are about to change violates Usability Heuristic Numero Uno:

Visibility of system status
    The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.

see http://www.useit.com/papers/heuristic/heuristic_list.html

So to fix this please show what bugs, including bug number and possibly the short_desc whenever any change to a bug occurs. 

As far as the severity of the problem. It could be high if this takes a while to do the match or the user gets interrupted.

This seems like an easy thing to fix as well.