Minimize the amount of oVirt blockers bugs on NEW status before the build day

Description

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 , 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

Assignee

infra

Reporter

Eyal Edri

Blocked By

None

Components

Priority

High

Epic Name

Improve prioritization of handing oVirt blockers bugs in time
Configure