Changes between Version 6 and Version 7 of TracTickets
- Timestamp:
- 06/06/09 18:16:19 (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracTickets
v6 v7 1 2 1 = The Trac Ticket System = 3 2 [[TracGuideToc]] 4 3 5 The Trac issuedatabase provides simple but effective tracking of issues and bugs within a project.4 The Trac ticket database provides simple but effective tracking of issues and bugs within a project. 6 5 7 6 As the central project management element of Trac, tickets are used for '''project tasks''', '''feature requests''', '''bug reports''' and '''software support issues'''. … … 11 10 An issue is assigned to a person who must resolve it or reassign the ticket to someone else. 12 11 All tickets can be edited, annotated, assigned, prioritized and discussed at any time. 13 14 '''Note:''' To make full use of the ticket system, use it as an ''in bucket'' for ideas and tasks for your project, rather than just bug/fault reporting.15 12 16 13 == Ticket Fields == … … 28 25 * '''Milestone''' - When this issue should be resolved at the latest. 29 26 * '''Assigned to/Owner''' - Principal person responsible for handling the issue. 30 * '''Cc''' - A list of other associated people. ''Note that this does not imply responsiblity or any other policy.''27 * '''Cc''' - A comma-separated list of other users or E-Mail addresses to notify. ''Note that this does not imply responsiblity or any other policy.'' 31 28 32 29 * '''Resolution''' - Reason for why a ticket was closed. One of {{{fixed}}}, {{{invalid}}}, {{{wontfix}}}, {{{duplicate}}}, {{{worksforme}}}. … … 37 34 '''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]. 38 35 36 '''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. 37 38 '''Note:''' Description of the builtin ''priority'' values is available at [wiki:TicketTypes#Whyistheseverityfieldgone] 39 39 40 40 == Changing and Commenting Tickets == … … 57 57 '''Note:''' See TracNotification for how to configure email notifications of ticket changes. 58 58 59 === State Diagram === 60 http://projects.edgewall.com/trac/attachment/wiki/TracTickets/Trac%20Ticket%20State%20Chart%2020040607DF.png?format=raw 61 59 '''Note:''' See TracWorkflow for information about the state transitions (ticket lifecycle), and how this workflow can be customized. 62 60 63 61 == Default Values for Drop-Down Fields == … … 65 63 The option selected by default for the various drop-down fields can be set in [wiki:TracIni trac.ini], in the `[ticket]` section: 66 64 67 * `default_type`: Default ticket type68 65 * `default_component`: Name of the component selected by default 69 * `default_version`: Name of the default version70 66 * `default_milestone`: Name of the default milestone 71 67 * `default_priority`: Default priority value 72 68 * `default_severity`: Default severity value 69 * `default_type`: Default ticket type 70 * `default_version`: Name of the default version 73 71 74 72 If any of these options are omitted, the default value will either be the first in the list, or an empty value, depending on whether the field in question is required to be set. … … 84 82 == Assign-to as Drop-Down List == 85 83 86 If the list of possible ticket owners is finite, you can change the ''assign-to'' ticket field from a text input to a drop-down list. This is done by setting the `restrict_owner` option of the `[ticket]` section in [wiki:TracIni trac.ini] to “true”. In that case, Trac will use the list of all users who have logged in and set their email addressto populate the drop-down field.84 If the list of possible ticket owners is finite, you can change the ''assign-to'' ticket field from a text input to a drop-down list. This is done by setting the `restrict_owner` option of the `[ticket]` section in [wiki:TracIni trac.ini] to “true”. In that case, Trac will use the list of all users who have accessed the project to populate the drop-down field. 87 85 88 ''Note that this feature is '''still experimental as of version 0.9'''. There is no way to only display a subset of all known users as possible ticket owners. Nor is there a convenient way to remove emeritus users short of directly modifying the database.'' 89 86 To 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 87 91 88 == Preset Values for New Tickets == … … 95 92 Possible variables are : 96 93 94 * '''type''' - The type droplist 97 95 * '''reporter''' - Name or email of the reporter 98 96 * '''summary''' - Summary line for the ticket … … 107 105 * '''cc''' - The list of emails for notifying about the ticket change 108 106 109 '''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui'' 107 '''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui''[[BR]] 110 108 111 112 See also: TracGuide, TracWiki, TracTicketsCustomFields, TracNotification 109 ---- 110 See also: TracGuide, TracWiki, TracTicketsCustomFields, TracNotification, TracReports, TracQuery
