"Triage" is a medical term. It refers to dividing wounded or sick people into three categories: those who will die no matter what you do, those who will recover even if unaided, and those who will recover only if aided. In a situation where there's too much to do, you must concentrate on the third group.

 “伤员鉴别分类"是一个医学词汇.指的是将受伤的或者生病的人分为三类：无药可救必死无疑的人，无需救治自己就ok的人，还有只有接受救治才能恢复的人。假设除此之外还有许多事情要做，你只有全身心投入到救治第三类人中去。

Bug Triage Meetings (sometimes called Bug Councils) are project meetings in which open bugs are divided into categories. The most important distinction is between bugs that will not be fixed in this release and those that will be

 缺陷分类会议是项目级别的将缺陷分类的一个会议。最重要的是分清楚哪些缺陷要不需要在当前版本修复，哪些需要。

There are three categories for the medical usage, software also three categories - bugs to fix now, bugs to fix later, and bugs we'll never fix

在医学上的分类有三种，在缺陷管理上也有三种:现在就要修复的缺陷，之后要修复的缺陷，和不会修复的缺陷。 

Triaging a bug involves:

 bug分类包括以下内容：

Making sure the bug has enough information for the developers and makes sense

确定缺陷相关信息对于开发人员来说足够详细充分，而且合理。

Making sure the bug is filed in the correct place

确定缺陷开启在正确的路径（在bug管理工具中，每个缺陷也有路径的）

Making sure the bug has sensible "Severity" and "Priority" fields

确定缺陷的严重级别，和优先级正确，合理。

Let us see what Priority and Severity means

 让我们了解以下什么是严重级别和优先级

Priority is Business;

优先级是从公司运营角度(人力配置，资金投入等）

Severity is Technical

 严重级别是从技术角度

In Triages, team will give the Priority of the fix based on the business perspective.  They will check “How important is it to the business that we fix the bug?”  In most of the times high Severity bug is becomes high Priority bug, but it is not always.  There are some cases where high Severity bugs will be low Priority and low Severity bugs will be high Priority. 

 在分类会上，团队会根据公司运营角度设置优先级。他们会考虑“我们修复这个缺陷对公司运营有多么重要？”。一般高严重级别的缺陷优先级别也高，但并不是一直都是这样。有时会出现的高严重级别缺陷有第优先级，低严重级别缺陷有一个高的优先级。

In most of the projects I worked, if schedule drawn closer to the release, even if the bug severity is more based on technical perspective, the Priority is given as low because the functionality mentioned in the bug is not critical to business. 

 在大多数我参与的项目，如果项目截至日期临近，即时有从技术层面看严重级别高的缺陷，但是优先级却不高，这是由于这个缺陷表明的功能问题对整个项目运作不是最关键的。

Priority and Severity gives the excellent metrics to identify overall health of the Project.  Severity is customer-focused while priority is business-focused.  Assigning Severity for a bug is straightforward.  Using some general guidelines about the project, testers will assign Severity but while assigning a priority is much more juggling act.  Severity of the bug is one of the factors for assigning priority for a bug.  Other considerations are might be how much time left for schedule, possibly ‘who is available for fix’, how important is it to the business to fix the bug, what is the impact of the bug, what are the probability of occurrence and degree of side effects are to be considered. 

 优先级和严重级别是两个很重要的指标对于项目整个开展过程来说。严重级别是从客户角度考虑，而优先级别是从项目运作考虑。设置严重级别很简单。根据一些指导文档测试人员就可以给出严重级别，而在给出优先级别时却要做更多的考量。另外需要注意是“项目周期所剩多少时间？”，“谁还有空能修复缺陷？”，“修复这个缺陷到底对于项目来说有多么重要？”，“这个缺陷会导致什么结果？","出现的频率如何？“，和”修复这个缺陷可能带来的其他问题”这些都是需要考虑的。

Read the excellent article Arguing Apples and Oranges