| 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` |
| | 5 | == Status and Resolution == |
| | 6 | * Don't close or reopen a ticket without a reason |
| | 7 | * `fixed` is used when the resolution of the ticket can be linked to some change in the repository, a code change, a primary documentation fix, a contribution script added, etc. Otherwise use: |
| | 8 | - `worksforme`: the problem reported was not really a problem; the requested feature is already implemented or can be obtained in a different way |
| | 9 | - `wontfix`: the problem reported is not really Trac's problem; the requested feature won't be implemented because we don't think it fits in the scope of the core of Trac. In some cases however (e.g. #2611), we let the issue open even if the cause of the issue is not directly Trac's fault, so that workarounds and user experience can be collected. |
| | 10 | - `invalid`: the ticket was a test ticket, intended for another Trac, etc. |
| | 11 | - `duplicate`: there's already another ticket about the same issue |
| | 12 | |
| | 13 | == Milestone == |
| | 14 | * If resolution is `fixed`, the Milestone should be set, otherwise it should be blank. |
| 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` |
| 30 | | * `notification` - any issue related to email notifications |
| 31 | | * `needinfo` - waiting on information from the reporter |
| | 30 | |
| | 31 | The purpose of keywords is to be able to generate pertinent and focused [TracQuery TracQueries], so use them appropriately. |
| | 32 | - General indications |
| | 33 | * [query:group=status&keywords~=needinfo needinfo] - |
| | 34 | waiting on information from the reporter |
| | 35 | * [query:group=status&keywords~=tobedeleted tobedeleted] - |
| | 36 | "noise" tickets that could eventually be safely deleted one day |
| | 37 | * [query:group=status&keywords~=helpwanted helpwanted] - tickets which are looking for contributors |
| | 38 | * [query:group=status&keywords~=review review] - |
| | 39 | peer review requested |
| | 40 | * [query:group=status&keywords~=documentation documentation] - |
| | 41 | things that need to be better documented |
| | 42 | * [query:group=status&keywords~=patch patch] - |
| | 43 | same as review keyword, but when a patch is created by a third party |
| | 44 | - Related to branches |
| | 45 | * [query:group=status&keywords~=workflow workflow] - |
| | 46 | waiting for workflow branch merge (see WorkFlow) |
| | 47 | * [query:group=status&keywords~=permissions permissions] - |
| | 48 | waiting for permissions branch merge (see PermissionPolicy) |
| | 49 | * [query:group=status&keywords~=xref xref] - |
| | 50 | related to the TracCrossReferences ideas |
| | 51 | * [query:group=status&keywords~=tracobject tracobject] - |
| | 52 | related to the generalization of the Trac object/resource concept (see TracObjectModelProposal and TracDev/Proposals/DataModel) |
| | 53 | - Related to backends |
| | 54 | * [query:group=status&keywords~=mysql mysql] |
| | 55 | * [query:group=status&keywords~=postgres postgresql] |
| | 56 | * [query:group=status&keywords~=sqlite pysqlite] |
| | 57 | * [query:group=status&keywords~=svn12 svn12x], [query:group=status&keywords~=svn13 svn13y], [query:group=status&keywords~=svn14 svn 14z], ... |
| | 58 | - Other kinds of grouping |
| | 59 | * [query:group=status&keywords~=unicode unicode] |
| | 60 | * [query:group=status&keywords~=notification notification] - |
| | 61 | any issue related to email notifications |
