Editing a bug targeted to a release crashes if you directly edit the untargeted task

Bug #106338 reported by Diogo Matsubara on 2007-04-13
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Critical
Graham Binns

Bug Description

Steps to reproduce (using sample data):
1. Open bug http://bugs.launchpad.dev/debian/+source/mozilla-firefox/+bug/3/+editstatus
2. Change any attribute, like status
3. Crash like OOPS-466C886

ConjoinedBugTaskEditError: This task cannot be edited directly, it should be
+edited through its conjoined_master.

Recent OOPSes: OOPS-1003EB184, OOPS-1003EB185, by editing the URL (+editstatus-page) and following the step 2

Also: OOPS-1187EC1485, OOPS-1187EC1486, OOPS-1223EC191

Related branches

Diogo Matsubara (matsubara) wrote :

Setting importance to low as this doesn't happen often and the needs manul URL editing to reach the edit bug status page.

Changed in malone:
importance: Undecided → Low
status: Unconfirmed → Confirmed
Ursula Junque (ursinha) on 2008-10-01
description: updated
description: updated
Ursula Junque (ursinha) on 2009-05-11
description: updated
Curtis Hovey (sinzui) on 2010-11-26
Changed in malone:
importance: Low → High
Changed in launchpad:
importance: High → Critical
Curtis Hovey (sinzui) wrote :

I think there are ways to reach this oops.

Experienced users know to hack +editstatus to the distribution bug. This is less common now that the UI does inline editing and it does not do it for the conjoined slave. This can still happen when there is a collision between someone who targets to the current series while someone else is changing the distribution bug. So while we do not want the +editstatus form to display for conjoined slaves, the view will still need to handle submit cases in __init__ or initialize(). I think the form needs to explain that only the master can be edited, and link to the master (the current targeted series). That message could be an info notifcation. The form field could be disabled, or the form not rendered at all.

The most common occurrence of this bug is via the API. I think ConjoinedBugTaskEditError should be converted to a HTTP error.

tags: added: api
j.c.sackett (jcsackett) on 2011-03-02
Changed in launchpad:
assignee: nobody → j.c.sackett (jcsackett)
j.c.sackett (jcsackett) on 2011-03-03
Changed in launchpad:
assignee: j.c.sackett (jcsackett) → Leonard Richardson (leonardr)
Curtis Hovey (sinzui) wrote :

This fix for this bug may also fix bug 556515.

Launchpad QA Bot (lpqabot) wrote :
Changed in launchpad:
milestone: none → 11.04
tags: added: qa-needstesting
Changed in launchpad:
status: Triaged → Fix Committed
Leonard Richardson (leonardr) wrote :

As it happens, the fix to bug 556515 did _not_ fix this bug. I should have linked but 556515 to my branch instead of this bug.

Changed in launchpad:
status: Fix Committed → Triaged
assignee: Leonard Richardson (leonardr) → nobody
tags: removed: api qa-needstesting
William Grant (wgrant) on 2011-03-16
tags: added: qa-untestable
tags: removed: qa-untestable
Curtis Hovey (sinzui) on 2011-04-11
Changed in launchpad:
milestone: 11.04 → none
Robert Collins (lifeless) wrote :

One way to fix this is just to reflect the edits onto the master too; alternatively if we can get rid of conjoined masters this issue will simply vanish.

Graham Binns (gmb) on 2011-05-25
Changed in launchpad:
assignee: nobody → Graham Binns (gmb)
status: Triaged → In Progress
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
Graham Binns (gmb) on 2011-05-30
tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant) on 2011-06-01
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers