Launchpad itself

bug activity log looks ugly (because it is a table)

Bug #6072 reported by Dafydd Harries
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

The bug activity log uses a table, which gets messy when it's recording changes to descriptions. It would be better for it to use a list.

Here's a good example of activity log ugliness:

https://launchpad.net/products/launchpad/+bug/3945/+activity

Interleaving activity with comments in the bug report page itself (bug 270268) would be one way of fixing this bug.

See original description
Dafydd Harries (daf)
Changed in malone:
assignee: nobody → mpt
Revision history for this message
Dafydd Harries (daf) wrote :

Here's an even worse offender:

https://launchpad.net/products/rosetta/+bug/1539/+activity

Revision history for this message
Martin Pool (mbp) wrote :

Some thoughts:

It's a bit strange that there are two chronological views of a bug: the regular comments, and the activity log.

The activity log could instead be conceived as showing more detail about the history of the bug: when activated, it would insert additional records between the comments on the regular page, showing the modifications made to fields. This could be called "show all activity", or "show detailed changes".

This would fix this particular bug but also, I think, give a better understanding of why the particular field changes were made by showing them in the context of the discussion.

Revision history for this message
Björn Tillenius (bjornt) wrote : Re: [Bug 6072] bug activity log should not use a table

On Mon, Feb 06, 2006 at 11:53:22PM -0000, Martin Pool wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/6072
>
> Comment:
> Some thoughts:
>
> It's a bit strange that there are two chronological views of a bug: the
> regular comments, and the activity log.
>
> The activity log could instead be conceived as showing more detail about
> the history of the bug: when activated, it would insert additional
> records between the comments on the regular page, showing the
> modifications made to fields. This could be called "show all activity",
> or "show detailed changes".
>
> This would fix this particular bug but also, I think, give a better
> understanding of why the particular field changes were made by showing
> them in the context of the discussion.

The plan is to move the activity log to the main bug page, and show the
changes together with the comments. This is specified in
https://wiki.launchpad.canonical.com/BugHistory

Diogo Matsubara (matsubara)
Changed in malone:
status: Unconfirmed → Confirmed
Matthew Paul Thomas (mpt)
Changed in malone:
assignee: mpt → bjornt
Diogo Matsubara (matsubara)
description: updated
Diogo Matsubara (matsubara)
description: updated
Matthew Paul Thomas (mpt)
description: updated
Björn Tillenius (bjornt)
Changed in malone:
assignee: Björn Tillenius (bjornt) → nobody
Robert Collins (lifeless)
summary: - bug activity log should not use a table
+ bug activity log looks ugly (because it is a table)
Changed in launchpad:
importance: Medium → Low
Revision history for this message
Bob Bib (bobbib) wrote :

IMHO, it would be useful to reflect description changes in a bug activity log using a diff-like style.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.