Comment 3 for bug 317244

The context table used to be hidden in duplicate bug reports. I un-hid it, and greyed it out instead, for two reasons.

First, the information is often useful in telling whether a duplicate marking is correct. If the duplicate is In Progress while the dup target is New, or the duplicate is assigned to someone while the dup target is not, or the duplicate is milestoned while the dup target is not, then the duplicate has most likely been marked in the wrong direction and the bug would be fixed faster if the direction was reversed. If QA people cannot see any of that information, they can't tell whether they should do that.

Second, where work is accidentally being done in parallel, the duplicate information needs to be merged usually by people other than those marking the duplicate. For example: Bug X is assigned to Fred, Confirmed, and targeted at milestone 1.2. Bug Y is assigned to Samantha, and In Progress, but targeted to 1.3. The reports are duplicates. Who should the winning report be assigned to? And if it is assigned to Samantha since she's started on it already, but she says she's unlikely to get it finished this cycle, which milestone should it be targeted to? A project manager or maintainer can make those decisions, but the QA minion who marks the duplicate probably cannot. QA people shouldn't have to feel hesitant about marking duplicates because they'll be hiding information that would be useful to managers or maintainers hours or days later.