Changes between Version 3 and Version 4 of TracTickets


Ignore:
Timestamp:
09/15/2009 02:30:03 (12 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracTickets

    v3 v4  
    1313== Ticket Fields ==
    1414
    15 '''Note:''' Sugar Labs' definitions are maintained here: [http://sugarlabs.org/go/BugSquad/StatusFields Status Fields].
    16 
    1715A  ticket contains the following information attributes:
    1816 
     
    2119
    2220 * '''Component''' - The project module or subsystem this ticket concerns.
    23  * '''Version''' - Version of Sugar that this ticket pertains to or where the bug has most recently been found.
     21 * '''Version''' - Version of the project that this ticket pertains to.
    2422 * '''Keywords''' - Keywords that a ticket is marked with.  Useful for searching and report generation.
    2523
     
    3634'''Note:''' Versions of Trac prior to 0.9 did not have the ''type'' field, but instead provided a ''severity'' field and different default values for the ''priority'' field. This change was done to simplify the ticket model by removing the somewhat blurry distinction between ''priority'' and ''severity''. However, the old model is still available if you prefer it: just add/modify the default values of the ''priority'' and ''severity'', and optionally hide the ''type'' field by removing all the possible values through [wiki:TracAdmin trac-admin].
    3735
    38 '''Note:''' the [wiki:TicketTypes type], [wiki:TicketComponent component], version, priority and severity fields can be managed with [wiki:TracAdmin trac-admin] or with the WebAdmin plugin.
     36'''Note:''' the [trac:TicketTypes type], [trac:TicketComponent component], version, priority and severity fields can be managed with [wiki:TracAdmin trac-admin] or with the [trac:WebAdmin WebAdmin] plugin.
    3937
    40 '''Note:''' Description of the builtin ''priority'' values is available at [wiki:TicketTypes#Whyistheseverityfieldgone]
     38'''Note:''' Description of the builtin ''priority'' values is available at [trac:TicketTypes#Whyistheseverityfieldgone TicketTypes]
    4139
    4240== Changing and Commenting Tickets ==
     
    6563The option selected by default for the various drop-down fields can be set in [wiki:TracIni trac.ini], in the `[ticket]` section:
    6664
     65
     66
     67
    6768 * `default_component`: Name of the component selected by default
    6869 * `default_milestone`: Name of the default milestone
     
    8788
    8889To appear in the dropdown list, a user needs be registered with the project, ''i.e.'' a user session should exist in the database. Such an entry is automatically created in the database the first time the user submits a change in the project, for example when editing the user's details in the ''Settings'' page, or simply by authenticating if the user has a login. Also, the user must have `TICKET_MODIFY` [TracPermissions permissions].
     90
     91'''Note:''' See [http://pacopablo.com/wiki/pacopablo/blog/set-assign-to-drop-down Populating Assign To Drop Down] on how to add user entries at database level
     92
     93'''Note 2:''' If you need serious flexibility and aren't afraid of a little plugin coding of your own, see [http://trac-hacks.org/wiki/FlexibleAssignToPlugin FlexibleAssignTo] (disclosure: I'm the author)
    8994
    9095== Preset Values for New Tickets ==