A new multi-line input titled "Scratchpad", which anyone with canconfirm/editbugs can edit, would provide a general-purpose solution for the needs described above. It would need revision-history support as any normal comment would, and would let people make use of it for a variety of use cases that would conflict if implemented less generically.
Bug 1525376 Comment 15 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
A new multi-line input titled "Scratchpad", which anyone with canconfirm/editbugs can edit, would provide a general-purpose solution for the needs described above. It would need revision-history support as any normal comment would, and would let people make use of it for a variety of use cases that would conflict if implemented less generically. I would hide it behind a button "Scratchpad" with a visual indicator of _whether_ content is present or not and who/when last-updated.
A new multi-line input titled **Scratchpad**, which anyone with canconfirm/editbugs can edit, would provide a general-purpose solution for the needs described above. It would need revision-history support as any normal comment would, and would let people make use of it for a variety of use cases that would conflict if implemented less generically. I would hide it behind a button "Scratchpad" with a visual indicator of _whether_ content is present or not and who/when last-updated.
A new multi-line input titled **Scratchpad**, which anyone with canconfirm/editbugs can edit, would provide a general-purpose solution for the needs described above. It would need revision-history support as any normal comment would, and would let people make use of it for a variety of use cases that would conflict if implemented less generically. I would hide it behind a button with a visual indicator of _whether_ content is present or not and who/when last-updated.