Launchpad itself

Record bugtask expiration

Bug #344207 reported by Gavin Panella
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Invalid
Medium
Unassigned

Bug Description

In doc/bugtask-expiration.txt it's apparent that the bug activity log records bugtask expiration only tangentially, when it records changes to statusexplanation. However, we will soon not be recording statusexplanation changes. Recording bug expiration in the bug activity log seems like a sensible thing to do, so we should ensure that the janitor adds a log entry explicitly.

Gavin Panella (allenap)
Changed in malone:
importance: Undecided → Medium
milestone: none → 2.2.3
status: New → Triaged
Revision history for this message
Björn Tillenius (bjornt) wrote :

I'm marking this bug as Invalid, since we don't expire bugs today, and when we do we'll probably have an Expired status.

Changed in malone:
milestone: 2.2.3 → none
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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