Changes between Version 65 and Version 66 of TracTicketTriage

Timestamp:

Mar 15, 2014, 1:32:10 PM (10 years ago)

Author:

Christian Boos

Comment:

… add the new standard disclaimer

TracTicketTriage

@@ -13 +13 @@
 
 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.
- - tickets which are targeting a software which has nothing to do with Trac should be closed as //invalid// with the WrongTrac mention in the comment
- - tickets which are targeting a Trac plugin should be closed as //cantfix// with the PluginIssue mention in the comment. If the identity of the plugin is easily determined, add the `TH:<Plugin>` mention.
-   - if the plugin is "agilo", then mention AgiloForScrum and add support@agile42.com to the CC: 
- - tickets which are clearly about installation issues or support requests should be invalidated as well, mentioning an InstallationIssue
+ - tickets which are targeting a software which has nothing to do with Trac should be closed as //invalid// with the **WrongTrac** mention in the comment
+ - tickets which are targeting a Trac plugin should be closed as //cantfix// with the **PluginIssue** mention in the comment. If the identity of the plugin is easily determined, add the `TH:<Plugin>` mention.
+   - if the plugin is "agilo", then mention **AgiloForScrum** and add support@agile42.com to the CC: 
+ - tickets which are clearly about installation issues or support requests should be invalidated as well, qualifying it as an **InstallationIssue**
+ - for complaints about the long inactivity on opened tickets, refer to **ThisTicketWasOpenedTenYearsAgo** 
 
 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.