Edgewall Software

Changes between Version 83 and Version 84 of TracTicketTriage


Ignore:
Timestamp:
Jan 18, 2016, 2:46:02 PM (4 years ago)
Author:
figaro
Comment:

Further cosmetic changes

Legend:

Unmodified
Added
Removed
Modified
  • TracTicketTriage

    v83 v84  
    33= Trac Project Ticket Triage
    44
    5 This page lists guidelines and conventions used within the Trac project for [http://en.wikipedia.org/wiki/Triage triage] of tickets.
     5This page lists guidelines and conventions used within the Trac project for [wikipedia:Triage triage] of tickets.
    66
    77We 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, such as query:status!=closed&milestone= or report:20.
     
    3232
    3333 * If resolution is `fixed`, the Milestone should be set according to the RoadMap. See report:36 for tickets that should be corrected.
    34  * If resolution is `duplicate`, `cantfix`, `wontfix`, `invalid` or `worksforme` the Milestone should be blank. See report:35 for tickets that should be corrected.
     34 * If resolution is `duplicate`, `cantfix`, `wontfix`, `invalid` or `worksforme`, the Milestone should be blank. See report:35 for tickets that should be corrected.
    3535 * If the ticket is valid and related to Trac, but no developer is planning to work on it for a next release, use [milestone:unscheduled].
    3636 * If the ticket is valid and related to Trac, but not directly related to a release, use [milestone:"not applicable"].
     
    4444== Status and Resolution
    4545
    46  `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. For ticket type '''task''', fixed is used even if there was no trackable change in the repository/documentation.
     46 `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. For ticket type '''task''', fixed is used even if there was no traceable change in the repository/documentation.
    4747 `worksforme`:: the problem reported was not really a problem; the requested feature is already implemented or can be obtained in a different way.
    48  `cantfix` / `wontfix` :: the problem reported is not really Trac's problem (use `cantfix` when we don't control the code involved); alternatively, the requested feature won't be implemented, because we don't think it fits in the scope of the core of Trac, or because the feature would be better implemented as a [wiki:TracPlugins plugin] (use `wontfix`).
     48 `cantfix` / `wontfix` :: the problem reported is not really Trac's problem (use `cantfix` when we don't control the code involved); alternatively, the requested feature won't be implemented, because we don't think it fits in the scope of the core of Trac and would therefore be better implemented as a [wiki:TracPlugins plugin] (use `wontfix`).
    4949   * '''Note''': 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.
    50    * '''Note''': If an API change is required to get a feature to work (that is intended to be implemented as a [wiki:TracPlugins plugin]), then a new ticket could be opened with the requested API changes. If it's not very clear what that change should be, it is preferable to keep the request for change next to the use case, ie keep that ticket opened for the purpose of the API change.
     50   * '''Note''': If an API change is required to get a feature to work (that is intended to be implemented as a [wiki:TracPlugins plugin]), then a new ticket could be opened with the requested API changes. If it's not clear what that change should be, then keep the request for change next to the use case, ie keep that ticket opened for the purpose of the API change.
    5151 `invalid`:: the ticket was a test ticket, intended for another Trac or something similar and should be closed as WrongTrac, PluginIssue or InstallationIssue.
    5252 `duplicate`:: there is already another ticket about the same issue:
     
    6565== Ticket Description
    6666
    67 Only administrators can edit ticket descriptions. They are only edited to fix formatting errors, not the actual content. Occasionally, we may also add editorial notes to not spread misleading information, e.g. #4297 or to summarize the current status of a long running issue, e.g. #4132 or #2611. In all cases, it should be quite clear from the formatting what's coming from the original author and what has been annotated afterwards.
     67Only administrators can edit ticket descriptions. They are only edited to fix formatting errors, not the actual content. Occasionally, we may also add editorial notes to not spread misleading information, eg #4297 or to summarize the current status of a long running issue, eg #4132 or #2611. In all cases, it should be quite clear from the formatting what's coming from the original author and what has been annotated afterwards.
    6868
    6969== Keywords