Yet we don't close out the issue, so it will keep some level of visibility in our system. Deferred issues may be addressed under a product development project, or if I need to find work for personnel during a slow period.
Issue severity gives management a good impression of the current state of the software being developed. It also serves as a foundation for establishing issue priority. Issue prioritization gives developers a clear understanding of the order in which they should work on their defects.
Despite the risk of "technical radicalism," when issue severity and priority travel hand in hand, managing developers can make informed decisions on work order and can support their choices with documented information.