Changing bug report to non-existent project loses accompanying comment
Bug #135435 reported by
Matthew Paul Thomas
This bug report is a duplicate of:
Bug #97338: Retargeting bug to unknown project/package loses the comment.
Edit
Remove
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
New
|
Undecided
|
Unassigned | ||
Bug Description
1. Open a bug report that is filed against a project.
2. Change the bug report's status, giving a detailed explanation in the "Comment on this change" field. Accidentally delete a character or two from the "Project" field, so that it has a value that is not registered as a project.
3. Click "Save Changes".
What should happen: The error is reported, with the form just how it was when you submitted it.
What actually happens: The error is reported, with the form just how it was when you submitted it ... except that the detailed comment you entered is GONE.
Workaround: Use the Back button.
Revision history for this message
| James Westby (james-w) wrote | #1 |
To post a comment you must log in.
Hi,
This bug just hit me as well. I didn't know the workaround
though, thanks Matthew.
Thanks,
James