Malone ate my editstatus comment
Bug #30861 reported by
Carlos Perelló Marín
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
The bug #5751 had a comment from the editstatus page when I fixed it.
After that, Malone was updated to store the editsatus comments as the other comments to that bug but the old editstatus comment was not migrated and only appear as "Comment on most recent change" at the editstatus.
Then, I had to reopen the bug and added a new comment using the editstatus form. It was added as a comment to the bug and the old editstatus commet just disappear.
Revision history for this message
| Brad Bollenbach (bradb) wrote | #1 |
| Changed in malone: | |
| status: | Unconfirmed → Rejected |
To post a comment you must log in.
Sorry for what appears to be strange behaviour.
We decided that the "Comment on most recent change" idea would be the way to deprecate the "status explation" field because:
* migrating the old status explanations to comments would have resulted in out-of-step comments in the bug discussion
* we found that status explanations generally contained no information that we couldn't afford to lose
Sorry again for the confusion, but I hope this helps clarify.