DB constraint triggered adding a new blueprint with status obsolete or superseded

Bug #121608 reported by Diogo Matsubara
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Critical
Curtis Hovey

Bug Description

Steps to reproduce (using sample data):
1. http://launchpad.dev/specs/+new
2. Fill in all required fields.
3. In 'Definition Status' choose Obsolete or superseded option
4. Click Register Blueprint
5. OOPS-537S47 IntegrityError ERROR: new row for relation "specification" violates check constraint "specification_completion_recorded_chk"

Related branches

description: updated
Curtis Hovey (sinzui)
Changed in blueprint:
importance: Undecided → Low
status: New → Triaged
Changed in launchpad:
importance: Low → Critical
Curtis Hovey (sinzui)
Changed in launchpad:
assignee: nobody → Curtis Hovey (sinzui)
status: Triaged → In Progress
Curtis Hovey (sinzui)
Changed in launchpad:
milestone: none → 11.03
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
William Grant (wgrant)
tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant)
Changed in launchpad:
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.