The back behaviour is confusing when reporting a bug and launchpad has issues.

Bug #1022334 reported by ill on 2012-07-08
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself

Bug Description

when submitting a bug to launchpad, if there is a timeout error, there is no way to save or recover the submitted data by hitting back button on browser

This bug is not about a timeout or oops, it is about the scripts that break the expected behaviour of the back button.

The form makes multiple ajax requests to change the state of the page, bug the state is not in the browser history. The back button is broken. One way to fix this issue is to use the YUI history module store each phase of the form to enable the back button.

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
hexafraction (rarkenin) on 2012-07-20
affects: ubuntu → apport (Ubuntu)

The back button in a browser works fine and is used by others to still submit bugs without issue

Changed in launchpad:
status: New → Invalid
ill (illumilore) wrote :

Wrong. It takes me back to the summary page that has "Please describe the bug in a few words, for example, "weather applet crashes on logout": " on it. When I put something in the summary box and hit next, then report new bug, the box further information does not have any of the previous information. I have tested this on multiple machines and it is completely reproducible on each one.

Changed in launchpad:
status: Invalid → New
Laura Czajkowski (czajkowski) wrote :

Can you please add the oops id when it happens here so we can look at it thanks

Changed in launchpad:
status: New → Incomplete
ill (illumilore) wrote :

Error ID: OOPS-8aa0ec6662671c24a69da35e5b47d533

Changed in launchpad:
status: Incomplete → New
summary: - data is not saved if launchpad has an error
+ The back behaviour is confusing when reporting a bug and launchpad has
+ issues.
Changed in launchpad:
status: New → Triaged
tags: added: ui
tags: added: timeout
Changed in launchpad:
importance: Undecided → Critical
Curtis Hovey (sinzui) on 2012-11-29
tags: added: bugs javascript
removed: bot-comment timeout
description: updated
Evan (ev) on 2012-11-30
Changed in apport:
status: New → Invalid
Adolfo Jayme (fitojb) on 2013-05-08
no longer affects: apport (Ubuntu)
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