status messages can take up quite a lot of space, you have to scroll past them, and it disturbs the discussion thread

[Morten Kjeldgaard]

"status messages can take up quite a lot of space, you have to scroll past them, and it disturbs the discussion thread".

One possible solution is to "move them to a special section". However, that would put pressure on commenters to describe the changes they were making, thereby adding more text you have to scroll past.

An alternative solution would be to make the status changes take up much less space, as shown in the original specification <https://dev.launchpad.net/BugHistory#Design>.

Another solution (not mutually exclusive) would be to have a toggle at the beginning of the history+comments for which things you want to see, as shown for example in the "Options" area of a Facebook profile page.
    *All Changes* | Comments | Other

good example(s):
  https://bugs.launchpad.net/udd/+bug/508258

[Matthew Paul Thomas (mpt)]

This bug report is confusing a problem with a suggested solution.

The problem is that the "status messages can take up quite a lot of space, you have to scroll past them, and it disturbs the discussion thread".

One possible solution is to "move them to a special section". However, that would put pressure on commenters to describe the changes they were making, thereby adding more text you have to scroll past.

An alternative solution would be to make the status changes take up much less space, as shown in the original specification <https://dev.launchpad.net/BugHistory#Design>.

Another solution (not mutually exclusive) would be to have a toggle at the beginning of the history+comments for which things you want to see, as shown for example in the "Options" area of a Facebook profile page.
    *All Changes* | Comments | Other

[Graham Binns (gmb)]

This is another one of those we-never-quite-finished it issues, this time for the activity log integration story.

Ideally, the activity items should be collapsible, per the original design.

[Robert Collins (lifeless)]

I've reopened this because, confused as it is, the problem is real on particularly busy bugs.