Severity - slander36/IssueTrackerTraining GitHub Wiki

Severity is the impactfulness of the issue on the end user, and can range anywhere from "that looks off" to "everything just crashed and it wiped my harddrive and keyed my car."

Example Severity tags

General Software - 1 lowest, 5 highest

1. Negligible (normally visual)(optional fix based on time)

• e.g. color is off on this element

2. Minor (visual or functional)(fix this month)

• e.g. color of key element deviates from company standard (i.e. Google logo using wrong red)

3. Major (functional)(fix this sprint)

• e.g. screen fails to resize properly, elements overlap but are still usable

4. Severe (functional)(fix by next build)

• e.g. Server receives response from client, but client isn't notified so page does not change. Multiple submissions are coming through because of this and clogging the logs

5. Show stopper (functional)(fix now and get new build out immediately)

• e.g. freezes on startup. Unable to load.

Games - 1 lowest, 5 highest

1. Negligible

• e.g. texture z-fighting (two overlapping textures flickering) in a section of the map normally ignored.

2. Minor

• e.g. final animation of three-hit-combo fails to play, but damage is still applied.

3. Major

• e.g. Currency increase is triple what it should be.

4. Severe

• e.g. Quest objective freezes player. Debug commands required to bypass quest. (Only severe because development/testing can resume and it is not a systemic issue. If this was for every quest, it would be a Show Stopper)

5. Show stopper

• e.g. Player freezes when dialog appears and cannot become unfrozen. No way to play/test the game.