When changing the status of a non-existent bugtask through wrong lp link, it changes anyway, and gives the user a 404 after that
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Medium
|
Eleanor Berger |
Bug Description
When trying to change the status of a non-existent bugtask for a bug, it changes the status anyway, and redirects the user to a 404 OOPS page.
Steps to reproduce:
1) Get a valid bug url in launchpad, https:/
https:/
2) Go to the link. You should see the "This bug isn't linked to firefox 3.0 (Ubuntu)" message.
3) Now change the status of the bug, and click "Save Changes".
It will change the status of the bugtask, but will fail with a 404, as seen in OOPS-1177EC92:
NotFound: Object: <canonical.
description: | updated |
tags: | added: oops |
summary: |
- I keep getting OOPS-1177EC92 when changing a bug + When changing the status of a non-existent bugtask through wrong lp + link, it changes anyway, and gives the user a 404 after that |
description: | updated |
Changed in launchpad: | |
milestone: | 2.2.3 → none |
Changed in malone: | |
milestone: | none → 2.2.3 |
Changed in malone: | |
milestone: | 2.2.3 → none |
The data is saved, but the user is redirected to the wrong page. Not a catastrophe, but it would be good to understand why this is happening.