• Immutable Page
• Info
• Attachments
• More Actions: Raw Text Print View Render as Docbook Delete Cache ------------------------ Check Spelling Like Pages Local Site Map ------------------------ Rename Page Delete Page ------------------------ Subscribe User ------------------------ Remove Spam Revert to this revision Package Pages Sync Pages ------------------------ Load Save SlideShow

• Launchpad entry: https://launchpad.net/products/malone/+spec/bug-history

• Created: 2005-10-03 by MatthewPaulThomas

• Contributors: MatthewPaulThomas

• Bugs:

  • #5443: Bug activity doesn't indicate changes to the product

  • #6072: bug activity log should not use a table

  • #807: Easy history view

  • #28741: activity log doesn't differentiate between the trackers

  • #28750: 2-column page layout is too narrow for bug activity table (+activity)

  • #34619: Activity log should show package reassignment

  • #45582: Activity log doesn't capture security flag changes

  • #56630: Tag changes are not recorded in the activity log

  • #65660: Activity log should capture milestone changes

  • #71840: Indicate in the main bug page who added the bugwatch

Summary

The history of every Malone bug report should be recorded thoroughly and presented unobtrusively for easy access from the bug page.

Rationale

Showing the history of a bug report on the bug page itself:

• increases accountability
• helps people understand what has happened to a bug report
• saves people from having to click back and forth between the bug report and the "activity log"
• makes it easy to see who fixed the bug first.

Use cases

• <seb128> you don't know who has closed a bug
  <seb128> when
  <seb128> why
  <seb128> etc
  <dholbach> there's an Activity Log
  <seb128> hum, that's hidden under "activity log"
  <dholbach> in the right ...
  <dholbach> yes
  <seb128> that's the crapiest interface ever

• Many months later, the same Sébastien Bacher marked bug 103420 as a duplicate. But because this action wasn't presented in the same place as his comment, Ian White didn't see the link to the original bug, so he asked: "Do you have the permalink to the original bug please?"

Design

Each action in the bug report should have a row that appears roughly like this.

• ◯

  ♟ Brad Bollenbach set ◙ launchpad importance High, status Confirmed.

  2006-01-18 19:09

The action of reporting the bug should have an expander ▶, clickable to show the original description.

• ▼	♟ Fred Fish reported the bug.	2006-01-18 12:24
  While trying to open my person page I got the error OOPS-18B7.

If text was changed, this should also be shown as as an expandable row.

• ▶	♟ Brad Bollenbach set ◙ launchpad importance High, and updated the report.	2006-01-18 19:06
  Ok, I found the Oops report.

When the row is expanded, it should show a highlighted diff (using the <del> and <ins> elements).

• ▼

  ♟ Brad Bollenbach set ◙ launchpad importance High, and updated the report.

  2006-01-18 19:06

  Description

  While trying to open my person page I got the error OOPS-18B7. Trying again later worked fine.

  While trying to open <https://launchpad.net/people/fredfish>: Oops-Id: OOPS-18B7 Exception-Type: ProgrammingError Exception-Value: ERROR: could not serialize access due to concurrent update UPDATE SessionData SET last_accessed = CURRENT_TIMESTAMP WHERE client_id = 'x-0YvxKnwgMj5.hrtVIb2Mg3zPcRR0m8tV- ypRXal2yZg2UMhsNeE0' AND last_accessed < CURRENT_TIMESTAMP - '600 seconds'::interval Date: 2006-01-18T00:37:52.861385+00:00 Trying again later worked fine.

  Summary

  Oops error

  ProgrammingError at person page

  Comment

  Ok, I found the Oops report.

Implementation

Code changes

Schema changes

Data migration

Unresolved issues

• Perhaps the expander should be on the right, rather than the left, to be closer to a browser window's scrollbar for someone scanning through a bug report.