Changes between Version 47 and Version 48 of TracTicketTriage

Timestamp:

Sep 5, 2007, 6:45:22 PM (17 years ago)

Author:

sid

Comment:

Add in cboos comments from the trac-dev mailing list about how to help

TracTicketTriage

@@ -4 +4 @@
 
 As a matter of fact, we happen to mainly focus on the Milestone information to decide whether a ticket has been triaged or not. Therefore, still to be triaged tickets can be found in queries specifying an unset milestone, like query:status!=closed&milestone= or report:20.
+
+== How to help? ==
+
+First, there is a good deal of tickets which are not yet triaged. Anyone with some knowledge about the Trac project can help us to apply the triaging rules, in order to detect duplicate requests, eliminate invalid tickets and identify the real issues by assigning them a milestone.
+
+For the tickets that are waiting for user feedback, anyone can help as well: close tickets which haven't received the requested feedback since a few months or further process them if they received some feedback.
+
+Finally, among the valid tickets, [http://trac.edgewall.org/query?status=new&status=assigned&status=reopened&group=milestone&milestone=%21&keywords=%21%7Eneedinfo&type=defect&order=priority many are categorized as defects]. Those should probably get the most attention or be recategorized as enhancements if they are not real defects.
 
 == Milestone ==