| | 1 | = Trac Project Ticket Triage = |
| | 2 | |
| | 3 | This page lists guidelines and conventions used within the Trac project for [http://en.wikipedia.org/wiki/Triage triage] of tickets. |
| | 4 | |
| | 5 | == General guidelines == |
| | 6 | * If resolution is `wontfix` or `worksforme`, the Milestone should be blank. |
| | 7 | * `fixed` is used for tickets that required a code change |
| | 8 | * otherwise use `wontfix` or `worksforme` |
| | 9 | * Don't assign a milestone without a reason or patch. |
| | 10 | * Don't modify a milestone as ''anonymous'' and without a reason. |
| | 11 | * If marking as `duplicate`, include referring ticket #s in both duplicate and duplicated tickets. |
| | 12 | * In duplicate ticket: ''This ticket is duplicate of #1234'' |
| | 13 | * In original request: ''#2345 has been marked as duplicate of this ticket'' |
| | 14 | |
| | 15 | == Ticket Title == |
| | 16 | * [PATCH] prepended - if you are the original ticket creator, then adding `[PATCH]` to the ticket title indicates a patch attached to ticket for review and integration that works for you. |
| | 17 | |
| | 18 | == Keywords == |
| | 19 | * `helpwanted` - tickets which are looking for contributors |
| | 20 | * `review` - peer review requested |
| | 21 | * `documentation` - things that need to be better documented |
| | 22 | * `patch` - same as review keyword, but when a patch is created by a third party |
| | 23 | * `workflow` - waiting for workflow branch merge |
| | 24 | * `permissions` - waiting for permissions branch merge |
| | 25 | * `xref` - waiting for the cross references branch merge |
| | 26 | * `mysql` |
| | 27 | * `postgresql` |
| | 28 | * `sqlite` |
| | 29 | * `unicode` |
