[Starlingx-discuss] bug severity and priority

[Xie, Cindy]

Bill/Ghada,
I am sending out my definition of bug severity and priority:

Bug Exposure or Severity	Definition
1- Critical	Product or key feature is not usable for intended purpose. 
2- High		Product or key feature is not reliably usable for intended purpose or use is significantly impaired
3 - Medium	Product or key feature is usable provided by a workaround
4 - Low		Tolerable impact to user experience with minimal service and support costs
	
Bug Priority	Definition
P1 - Stopper	Resolution of this defect takes precedence over other defects and most other development activities. This level is used to focus maximum development team resources to resolve a defect in the shortest possible timeframe. 
P2 - High	Resolution of the defect has precedence over resolving other defects with lesser classifications of priority.  The urgency to fix a P2 priority  defect is imminent. - P2 priority defects are intended to be resolved by the next planned external release of the software.
P3 - Medium	Resolution of the defect has precedence over resolving other defects with lesser classifications of priority.  - P3 priority defects must have a planned timeframe for a verified resolution.
P4 - Low	Resolution of the defect has least urgency to resolve, P4 priority defects may or may not have plans to resolve.

Let's discuss this and agree how we'd like to use them. My suggestion for current "Medium" is to we can mark them as "stx.3.0" and then in the beginning of stx.3, they can move Priority to "high" due to the fact they want to get them fixed in 3.0.

But the bug severity should never change because they are standard.

Thx. - cindy