User can publish silos set to 'QA Failed'

Bug #1496326 reported by Jean-Baptiste Lallement on 2015-09-16
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
CI Train [cu2d]
Fix Released
Medium
Robert Bruce Park

Bug Description

It is currently possible to publish, by mistake, a silo marked 'QA failed'.

It shouldn't be possible or the system should ask for a confirmation from the user before proceeding with the publication.

Related branches

Changed in cupstream2distro:
assignee: nobody → Łukasz Zemczak (sil2100)
status: New → Confirmed
importance: Undecided → Medium
Changed in bileto:
status: New → Won't Fix
Changed in cupstream2distro:
status: Confirmed → In Progress
no longer affects: bileto
Changed in cupstream2distro:
assignee: Łukasz Zemczak (sil2100) → Robert Bruce Park (robru)
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:cupstream2distro at revision 1108, scheduled for release in cupstream2distro, milestone Unknown

Changed in cupstream2distro:
status: In Progress → Fix Committed
Changed in cupstream2distro:
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