How to classify my bug?

Here a short list on how to classfiy a bug for one of our products.

  1. Highest – Reserved for catastrophic failures – exceptions, crashes, corrupt data, etc. that (a) prevent somebody from completing their task, and (b) have no workaround. These should be extremely rare. They must be fixed immediately and deployed as hotfixes.
  2. High – These may refer to unhandled exceptions or to other „serious“ bugs that only happen under certain specific conditions (i.e. a practical workaround is available). No hard limit for resolution time, but should be fixed within the next weeks (hotfix) and must be fixed by next release. The key distinction between (1) and (2) is not the severity or impact but the existence of a workaround.
  3. Medium – Usually reserved for perf issues. Anything that seriously hampers productivity but doesn’t actually prevent work from being done. Fix by next release.
  4. Low– These are „nuisance“ bugs. A default setting not being applied, a read-only field showing as editable (or vice-versa), a race condition in the UI, a misleading error message, etc. Fix for this release if there are no higher-priority issues, otherwise the following release.
  5. Lowest – Cosmetic issues. Scroll bars appearing where they shouldn’t, window doesn’t remember saved size/location, typos, last character of a label being cut off, that sort of thing. They’ll get fixed if the fix only takes a few minutes and somebody’s working on the same screen/feature at the same time, otherwise, maybe never. No guarantee is attached to these.

Back to service desk