The two dependency fields on show_bug show bug numbers. If there's an alias, it should display it instead, both for the read-only hyperlink and the editable text field.

what happens if someone changes which bug owns that alias while someone is viewing the bug?

Perhaps a relevant alias->bug mapping embedded in hidden fields would be the appropriate solution.

Actually upon reflection this is an issue for most fields, one that we have done nothing about (and my suggested implementation or similar has been suggested before for it). It might be more prevalent for aliases though.

i can't mark blocking 3.2. I agree with Matthew Tuck's suggestion. use a hidden mapping. We can use this to generate a midair collision. We should actually improve collisions to offer (*) Colliding ( ) Unchanged user value ( ) Pick something new: [ |v] But that's not necessary. I think that if we implement this and one other thing, I can probably make a proposal to deal with the problem of detecting whether bugs are in versions / should block releases.

This is obviously not a blocker, as it is an enhancement.

If a public bug blocks a security-sensitive bug, and the security-sensitive bug has an alias, should people not in the security group see the alias when they load the public bug?

(In reply to comment #6) > If a public bug blocks a security-sensitive bug, and the security-sensitive bug > has an alias, should people not in the security group see the alias when they > load the public bug? > Of course not.

Already implemented in Bugzilla 3.4.