Activity log should show package reassignment

Bug #34619 reported by Paul Sladen
8
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Gavin Panella

Bug Description

When a bug is reassigned from one package to a new one, the activity log afterwards continues to report the old package name the following link:

  https://launchpad.net/distros/ubuntu/+source/gnome-applets/+bug/34521/+activity

The "what changed" entry is marked as 'ubuntulooks', even though the target package has now been changed to 'ubuntu-artwork'. This looks like the bug is on two packages, since there's no entry to the reassignment from 'ubuntulooks' to 'ubuntu-artwork'

Revision history for this message
Stuart Bishop (stub) wrote : Re: [Bug 34619] On reassignment, activity log reports old assigned package name

Paul Sladen wrote:

> When a bug is reassigned from one package to a new one, the activity log
> afterwards continues to report the old package name.

>
> The "what changed" entry is marked as 'ubuntulooks', even though the
> target package has now been changed to 'ubuntu-artwork'.

This behavior is actually by design, as it is supposed to be a historical
log and retroactively rewriting history when the target package changes is a
loss of information.

The bug here is actually seems to be that there is no entry for when the
target was changed from ubuntulooks to ubuntu-artwork.

--
Stuart Bishop <email address hidden> http://www.canonical.com/
Canonical Ltd. http://www.ubuntu.com/

Revision history for this message
Paul Sladen (sladen) wrote : Re: [Bug 34619] On reassignment, activity log reports old assigned package name

> is supposed to be a historical log and retroactively rewriting history

I wasn't thinking of retrospectively rewriting it; but having the name
change at the point of reassignment. (Older entries have the previous
assignment, newer show the new name).

> The bug here is actually seems to be that there is no entry for when the
> target was changed from ubuntulooks to ubuntu-artwork.

Yup, that too :)

description: updated
Changed in malone:
assignee: nobody → bjornt
status: Unconfirmed → Confirmed
Revision history for this message
Björn Tillenius (bjornt) wrote :

This won't be done for 1.1.7, it's better to spend time re-writing the activity log, instead of making improvements to the current implemenation.

Revision history for this message
Matthias Klose (doko) wrote :

seen in #153263 as well, this obfuscates bug history much. there's no trace at all in the report

Gavin Panella (allenap)
Changed in malone:
importance: Medium → High
assignee: bjornt → nobody
description: updated
Gavin Panella (allenap)
Changed in malone:
milestone: none → 2.2.3
Gavin Panella (allenap)
Changed in malone:
assignee: nobody → allenap
status: Triaged → In Progress
Gavin Panella (allenap)
Changed in malone:
status: In Progress → Triaged
Graham Binns (gmb)
Changed in malone:
status: Triaged → In Progress
Revision history for this message
Björn Tillenius (bjornt) wrote : Bug fixed by a commit

Fixed in devel r8108.

Changed in malone:
status: In Progress → Fix Committed
Changed in malone:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

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