Changes between Version 1 and Version 2 of TracTickets
- Timestamp:
- 06/30/08 15:21:23 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracTickets
v1 v2 2 2 [[TracGuideToc]] 3 3 4 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. 5 5 6 6 As the central project management element of Trac, tickets are used for '''project tasks''', '''feature requests''', '''bug reports''' and '''software support issues'''. … … 25 25 * '''Milestone''' - When this issue should be resolved at the latest. 26 26 * '''Assigned to/Owner''' - Principal person responsible for handling the issue. 27 * '''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.'' 28 28 29 29 * '''Resolution''' - Reason for why a ticket was closed. One of {{{fixed}}}, {{{invalid}}}, {{{wontfix}}}, {{{duplicate}}}, {{{worksforme}}}. … … 34 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]. 35 35 36 '''Note:''' the ''type'' (TicketTypes), ''component'' (TicketComponent), ''version'' (TicketVersion), ''priority'' (TicketPriority) and ''severity'' (TicketSeverity) fields can all be managed through [wiki:TracAdmin trac-admin]. 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] 37 39 38 40 == Changing and Commenting Tickets == … … 55 57 '''Note:''' See TracNotification for how to configure email notifications of ticket changes. 56 58 57 === State Diagram === 58 [[Image(http://projects.edgewall.com/trac/attachment/wiki/TracTickets/Trac%20Ticket%20State%20Chart%2020060603DF.png?format=raw)]] 59 59 '''Note:''' See TracWorkflow for information about the state transitions (ticket lifecycle), and how this workflow can be customized. 60 60 61 61 == Default Values for Drop-Down Fields == … … 82 82 == Assign-to as Drop-Down List == 83 83 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 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. 85 85 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 . Also, the user must have `TICKET_MODIFY` [TracPermissions permissions].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]. 87 87 88 88 == Preset Values for New Tickets == … … 105 105 * '''cc''' - The list of emails for notifying about the ticket change 106 106 107 '''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui'' 107 '''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui''[[BR]] 108 108 109 109 ---- 110 See also: TracGuide, TracWiki, TracTicketsCustomFields, TracNotification 110 See also: TracGuide, TracWiki, TracTicketsCustomFields, TracNotification, TracReports, TracQuery
