Launchpad itself

When changing the status of a non-existent bugtask through wrong lp link, it changes anyway, and gives the user a 404 after that

Bug #346876 reported by John Vivirito
4
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://bugs.staging.launchpad.net/ubuntu/+source/firefox/+bug/139829, for instance. Now, change the package name to one that the bug doesn't have any bugtasks of, like firefox-3.0. So you'll have:
https://bugs.staging.launchpad.net/ubuntu/+source/firefox-3.0/+bug/139829
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.launchpad.database.bugtask.NullBugTask object at 0x2aaab27c6f90>, name: u'+editstatus'

See original description
Tags: lp-bugs oops
Revision history for this message
Eleanor Berger (intellectronica) wrote :

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.

Changed in launchpad:
assignee: nobody → intellectronica
importance: Undecided → Medium
milestone: none → 2.2.3
status: New → Triaged
Ursula Junque (ursinha)
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
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

Fixing bug 246041 (and bug 153763), by redirecting any non-existent/disabled context to an existing one, would also fix this bug.

Björn Tillenius (bjornt)
Changed in malone:
milestone: 2.2.3 → none
Revision history for this message
John Vivirito (gnomefreak) wrote :

I havent run into this bug for a while. Has it been fixed?

Revision history for this message
Eleanor Berger (intellectronica) wrote :

We now redirect to the primary task, instead of the null bugtask, for project tasks. This still needs to be done for packages, and then we can consider this fixed.

Revision history for this message
John Vivirito (gnomefreak) wrote : Re: [Bug 346876] Re: When changing the status of a non-existent bugtask through wrong lp link, it changes anyway, and gives the user a 404 after that

On 05/28/2009 08:51 AM, Tom Berger wrote:
> We now redirect to the primary task, instead of the null bugtask, for
> project tasks. This still needs to be done for packages, and then we can
> consider this fixed.
>
 Sounds good. Thanks for the update on it

--
Sincerely Yours,
    John Vivirito

https://launchpad.net/~gnomefreak
https://wiki.ubuntu.com/JohnVivirito
Linux User# 414246

"How can i get lost, if i have no where to go"
    -- Metallica from Unforgiven III

Revision history for this message
John Vivirito (gnomefreak) wrote :

I no longer see this in edge at least not in a while. Has this been updated in non-edge launchpad? If so can we close this or more work is being done?

Revision history for this message
Matthew Paul Thomas (mpt) wrote :

Fixed by fixing bug 246041.

Changed in malone:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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