Abolish the "statusexplanation" database field

Bug #88545 reported by Matthew Paul Thomas on 2007-02-27
26
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
High
Nigel Babu

Bug Description

When I originally proposed the "status explanation" field for bug reports, I thought it would be a way of presenting information that was relevant only to one particular project affected by the bug, without spamming people who weren't interested in that project. But this could never work, because there are no bugtask-specific lists of subscribers, so everyone gets mailed regardless (see bug 3529).

The term "status explanation" is now hidden, except in the activity log, where it causes confusion because it makes some bug comments show up and others not (see bug 88531). Since it doesn't and will never serve any useful purpose, the database field should be abolished.

See also bug 57414.

Related branches

description: updated
description: updated
Revision history for this message
Diogo Matsubara (matsubara) wrote :

Gavin fixed bug #249890 which removed the status explanation from the UI.

description: updated
Changed in malone:
status: New → Triaged
Revision history for this message
Druciferre (drewchapin) wrote :

O.O oops... Umm... This should still be Triaged, not Invalid... So if someone could fix that ?

I hovered my cursor over the status and saw an icon, I clicked on the icon thinking it might be an explanation of the status, and I accidentally clicked on "Invalid" instead of the X button to close the pop-up.

Changed in malone:
status: Triaged → Invalid
Gavin Panella (allenap) on 2009-09-17
Changed in malone:
status: Invalid → Triaged
importance: Undecided → Low
Revision history for this message
Robert Collins (lifeless) wrote :

We can shrink our DB size by dropping this - we have some real crap in it.

 select sum(length(statusexplanation)) from bugtask;
   sum
----------
 61701228

(60MB, which isn't /huge/ but isn't inconsequential either - and we're paying it on all bugtask loads).

summary: - Abolish the "status explanation" database field
+ Abolish the "statusexplanation" database field
Changed in launchpad:
importance: Low → High
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
Changed in launchpad:
assignee: nobody → Nigel Babu (nigelbabu)
tags: added: qa-needstesting
Changed in launchpad:
status: Triaged → In Progress
William Grant (wgrant) on 2011-09-12
tags: added: qa-ok
removed: qa-needstesting
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
removed: qa-ok
William Grant (wgrant) on 2011-09-15
tags: added: bad-commit-10978
Revision history for this message
William Grant (wgrant) wrote :

r13932 is OK, but the DB patch in r10978 is bad (r13932 is not deployed everywhere yet).

tags: added: qa-ok
removed: qa-needstesting
Revision history for this message
William Grant (wgrant) wrote :

The DB patch was reverted in r10981.

Revision history for this message
Launchpad QA Bot (lpqabot) wrote :

Fixed in db-stable r10978 (http://bazaar.launchpad.net/~launchpad-pqm/launchpad/db-stable/revision/10978) by a commit, but not testable.

tags: added: qa-untestable
removed: qa-ok
Changed in launchpad:
status: In Progress → Fix Committed
William Grant (wgrant) on 2011-09-16
Changed in launchpad:
status: Fix Committed → In Progress
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
removed: qa-untestable
Changed in launchpad:
status: In Progress → Fix Committed
Revision history for this message
Nigel Babu (nigelbabu) wrote :

< flacoste> nigelb: 2011-09-29 15:37:48 INFO 2208-84-1 applied just now in 0.3 seconds

tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant) on 2011-09-30
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related blueprints