Visibly show changed fields

[Paul Sladen]

Current Launchpad displays lots of fields in drop-downs, but it may be unclear which ones have been modified and which ones are unchanged.

It might be useful if Launchpad could outline updated fields; perhaps displaying a 1px green outline around any boxes that have been altered from their original database state.

The same system could be extended to use eg. 1px dotted green for updated and "good", 1px dashed outline for updated and incomplete fields, and 1px solid red outline for fields that cannot be updated because the situation is not allowed.

Ideally the pages would contain a duplicate form with the original data (or hashes of the field contents) so that it can be easily detected when the input field has been returned to its original state.

[Paul Sladen (sladen)]

  Importance: Wishlist

[Martin Albisetti (beuno)]

I... don't understand at all.
Which fields? in which form? while doing what?

[Matthew Paul Thomas (mpt)]

One example would be bug reports. I'm not sure if there are other examples.

Once changes are possible without page loads, one way to show which fields have changed would be to put the mini Confirm button next to only those fields.

For example, a bug in Incomplete status would have "Incomplete" as plain text but underlined in some way to show its clickability. Clicking it would turn it into a menu of statuses with a mini Cancel button next to it. But only when the menu selection was changed would the mini Confirm button appear next to the Cancel button.

_Incomplete_
      ↓
[Incomplete :⟠] (✘)
      ↓
[Confirmed :⟠] (✘) (✔)
      ↓
_Confirmed_

[Paul Sladen (sladen)]

Martin: sorry if the phrase "drop-down" was misleading. Drop-box in this case was referring to clicking just below "Affects" in the bug tracker and to all of the input fields that appear (Project, Status, Importance, Assigned to, ...).