Changes between Version 53 and Version 54 of TracTicketTriage

Timestamp:

Mar 17, 2009, 1:59:27 PM (15 years ago)

Author:

Christian Boos

Comment:

link to triage reports for wrongly assigned milestones

TracTicketTriage

@@ -27 +27 @@
  * If the bug or feature seems doable in a reasonable time frame, but doesn't seem to fit in the current schedule, use [milestone:1.0]
  * If there's no milestone corresponding to a past or future Trac release which seems to be adequate, but the ticket is nevertheless valid and has to be processed further, then the milestone can be set to [milestone:"not applicable"]. This rule is needed as long as we don't have a better way to distinguish among triaged and non-triaged tickets.
+
+See also report:35 and report:36 for the tickets that ''don't'' fulfill the first two requirements and that should be corrected one day.
 
 == Status and Resolution ==