OOPS claiming a merge proposal

Bug #507487 reported by Diogo Matsubara
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Paul Hummer

Bug Description

Steps to reproduce:
1. Create a merge proposal and assign it to the the default review team. (e.g. https://code.staging.launchpad.net/~matsubara/oops-tools/u1-summaries/+register-merge)
2. Go to the unclaimed merge propsal page assigned to the review team. (e.g. https://code.staging.launchpad.net/~matsubara/oops-tools/u1-summaries/+merge/17060)
3. Using the ajax comment at the bottom, leave a comment and approve the merge proposal
4. The table at the middle will still show the MP as "claimable" assigned to the default review team.
5. Click the "Claim review" button
6. OOPS-1474EB604 ClaimReviewFailed: The review is not pending.

What should happen: On step 3, the table shown on step 4 should be updated with the new state for the MP

Tags: lp-code oops

Related branches

Revision history for this message
Paul Hummer (rockstar) wrote :

This will be fixed when bug #496532 is fixed.

Changed in launchpad-code:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Paul Hummer (rockstar)
milestone: none → 10.01
Revision history for this message
Paul Hummer (rockstar) wrote :

Cooking in ec2 now!

Revision history for this message
Paul Hummer (rockstar) wrote :

Merged in db-devel 8911

Changed in launchpad-code:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in launchpad-code:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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