Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • Hmm, I think a bug that would damage data is more severe than something that is just annoying like say some functionality taking too long to load. Both should be fixed but those with higher negative impact should be fixed first. Commented Dec 1, 2015 at 9:43
  • No, as I wrote I know what they are or how to set them. I just do not se ethe benefit. Commented Dec 1, 2015 at 9:56
  • 6
    "The severity level, helps us identify..." Commented Dec 1, 2015 at 10:52
  • In most cases, no. But there are always edge cases where it makes sense to separate the two. Whether the separation is worth maintaining for every issue just to cater for those rare occasions is another matter. Commented Dec 1, 2015 at 11:49
  • 1
    You can have a UI bug that doesn't really affect he apps usability (low severity), but is a high priority because it's ugly. You can have a bug that crashes the app completely (high severity) but is a low priority because the conditions to make it happen are one in a million and in all practical terms will never actually happen (this ignores the fact that one-in-a-million chances come up nine times out of ten). Commented Dec 3, 2015 at 20:47