Known defects, or bugs, have a severity level that indicates the priority of the defect. Development managers usually define bug severity. Severity helps the product team focus on bug fixes for future releases and prioritize fixes.
The following table describes bug severity levels:
Reasonably common circumstances cause the entire system to fail, or a major subsystem to stop working, or other devices on the network to be disrupted. No workarounds exist.
Important functions are unusable and workarounds do not exist. Other functions and the rest of the network is operating normally.
Failures occur in unusual circumstances, or minor features do not work at all, or other failures occur but low-impact workarounds exist.
This is the highest level for documentation bugs.
Failures occur under very unusual circumstances, but operation essentially recovers without intervention. Users do not need to install any workarounds and performance impact is tolerable.
Defects do not cause any detrimental effect on system functionality.
Requests for new functionality or feature improvements.
Search for Bugs
Use the Bug Search page to obtain more information about a bug.