Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

We need an agreed definition or understanding on the priority of the bugs we find during testing. The following is my suggested approach, but I am open to feedback

 

RatingActionUrgency

Highest

Must be fixedWithin 24 hours of being raised if at all possible(as it delays other testing)
HighMust be fixedWithin one week if at all possible, to clear cases and stories as early as possible
MediumMust be fixedShould be fixed before go live but can be delayed so long as fixed before the end of the project
LowShould be fixedShould be fixed while there is a project, but can be left for BAU
LowestNo action requiredWe can live with it as is, indefinately
  • No labels