A severity level is just a tag to help the developers sort through the bugs. You should use one of the standard severity level wiki-words (don't create your own, or the developers will not "see" it):
- ProgramCrashes - self explanatory
- NumericalError - program runs to completion, but output shows numerical error
- CompileError - program will not even compile
- LinkError - individual modules all compile separately, but the final "link" stage croaks (often "unresolved external" errors)
Optionally, you can use the IEEE classifications:
- ProactiveCorrection - also known as "preventative maintenance": "modification of a software product after delivery to detect and correct latent faults ... before they become effective faults"
- ProactiveEnhancement - sometimes refered to as "perfective maintenance": "modification of a software product after delivery to improve performance or maintainability"
- ReactiveCorrection - also called "corrective maintenance" or a "bug fix": "reactive modification of a software product after delivery to correct discovered problems"
- ReactiveEnhancement - also called "adaptive maintenance": "modification of a software product after delivery to keep the product usable in a changed or changing environment"
To use these tags, just insert the word-string into your bug-report (exactly as shown, with no spaces) and it will be "found" by the search system.
