Retargeting bug to unknown project/package loses the comment

Bug #97338 reported by Matthias Klose
30
Affects Status Importance Assigned to Milestone
Launchpad itself
Won't Fix
Medium
Unassigned

Bug Description

- Retarget a bug report (e.g. <http://staging.launchpad.net/bugs/3> to a project or package that doesn't exist, including a comment as you do so.
- a page shows up, pointing out the non existing package, the text field is now empty.
- submit the fixed package name; the comment is not added.

It may save time to fix this bug at the same time as bug 78889.

Tags: lp-bugs
Changed in malone:
status: Unconfirmed → Confirmed
Revision history for this message
Daniel Hahler (blueyed) wrote :

Wow.. I've just arrived here after wandering through duplicates, invalidated bugs etc...
And this is still not fixed? :)

It seems like when an error is displayed after sending the bug changing form (the header area), or IIRC from another bug: when displaying errors in general, the comment (from the header area) gets lost.

This is a serious issue, because it can eat comments, as it happens in Konqueror 4 just now. In FF3 I could go back and the comment was there again.

Please fix it, because this is a tiny issue with an huge annoyance factor.

Changed in malone:
importance: Undecided → Medium
description: updated
description: updated
Revision history for this message
Robert Collins (lifeless) wrote :

We now have an ajax popup rather than the manual form (though the form still exists). I'm going to wontfix this: if using the non-ajax form your browser is capable of saving the state - just hit back. IF you're using the ajax, its seamless.

Changed in launchpad:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related blueprints

Remote bug watches

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