eyal edri created OVIRT-2206: -------------------------------- Summary: Minimize the amount of oVirt blockers bugs on NEW status before the build day Key: OVIRT-2206 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2206 Project: oVirt - virtualization made easy Issue Type: Epic Components: Bugzilla Automation Reporter: eyal edri Assignee: infra Priority: High As an oVirt maintainer or project lead, I would like to ensure all the blocker+ bugs are not in NEW status for the 2nd and 3rd build ( which is the last one per oVirt 4.2.z release ). This means that any bug that has a blocker+ flag on it should be taken into consideration as a first priority for the next sprint. This was requested by [~dfediuck], and might include a few user stories as smaller cards which will be assigned with this Epic. Examples for taking actions: * Mapping Bugzilla to JIRA issues that a bug with 'blocker+' will automatically get Blocker priority * Adding Bugzilla Whine to alert on such bugs - should be immediate and easy as initial MVP for this card * Increasing visibility for blocker bugs in JIRA with colors or flags. cc [~amarchuk] [~sbonazzo@redhat.com] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)