117481 - bug security settings on show_bug use too much space

Status: RESOLVED DUPLICATE of bug 524251

(Bugzilla :: User Interface, defect, P4)

Description

[John Vandenberg]

The security settings of a bug are usually best left alone, and they do not
change frequently.  For them to consume as much space as the comment field is
undesirable, especially as the amount of space required is due to the settings
being readily editable.

Ideally I would like a security summary (1 or 2 lines) placed inline with a link
to another page to alter the settings, where they are out of sight from the
casual user/developer.

If that is not acceptable/desirable then perhaps a few of the extra <br>'s could
be removed.  The (comments) could also be placed more conservatively.

Comment 1

[Matthew Tuck [:CodeMachine]]

Going to other pages is hard, that's why we can't add new attachments inline.

But we can investigate for 2.18.

Comment 2

[Vaskin Kissoyan]

There should be an option to have the default link show the "Format For
Printing" version and provide an EDIT buttom to go to the forms-based screen we
all know and love as our editing tool.

For a lot of users that only review bugs and don't actually edit them, this
should be the default view, maybe a comments window. The rest like the security
settings and others mentioned should be in the "Advanced" edit or view screen.

Comment 3

[Dave Miller [:justdave]]

The User Interface component now belongs to Gerv.  Reassigning all UNCONFIRMED
and NEW (but not ASSIGNED) bugs currently owned by Myk (the previous component
owner) to Gerv.

Comment 4

[Dave Miller [:justdave]]

Reassigning back to Myk.  That stuff about Gerv taking over the User Interface
component turned out to be short-lived.  Please pardon our confusion, and I'm
very sorry about the spam.

Comment 5

[Joel Peshkin]

Unloved bugs targetted for 2.18 but untouched since 9-15-2003 are being
retargeted to 2.20
If you plan to act on one immediately, go ahead and pull it back to 2.18.

Comment 6

[Max Kanat-Alexander]

This bug has not been touched by its owner in over six months, even though it is
targeted to 2.20, for which the freeze is 10 days away. Unsetting the target
milestone, on the assumption that nobody is actually working on it or has any
plans to soon.

If you are the owner, and you plan to work on the bug, please give it a real
target milestone. If you are the owner, and you do *not* plan to work on it,
please reassign it to [e-mail] or a .bugs component owner. If you are
*anybody*, and you get this comment, and *you* plan to work on the bug, please
reassign it to yourself if you have the ability.