Changes between Version 2 and Version 3 of TracTickets
- Timestamp:
- 10/18/2009 05:01:52 PM (11 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracTickets
v2 v3 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}}}. 30 * '''Status''' - What is the current status? See TracWorkflow30 * '''Status''' - What is the current status? One of {{{new}}}, {{{assigned}}}, {{{closed}}}, {{{reopened}}}. 31 31 * '''Summary''' - A brief description summarizing the problem or issue. 32 32 * '''Description''' - The body of the ticket. A good description should be specific, descriptive and to the point. … … 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 [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. 37 38 '''Note:''' Description of the builtin ''priority'' values is available at [trac:TicketTypes#Whyistheseverityfieldgone TicketTypes] 37 39 38 40 == Changing and Commenting Tickets == … … 55 57 '''Note:''' See TracNotification for how to configure email notifications of ticket changes. 56 58 59 '''Note:''' See TracWorkflow for information about the state transitions (ticket lifecycle), and how this workflow can be customized. 60 57 61 == Default Values for Drop-Down Fields == 58 62 59 63 The option selected by default for the various drop-down fields can be set in [wiki:TracIni trac.ini], in the `[ticket]` section: 64 65 66 60 67 61 68 * `default_component`: Name of the component selected by default … … 78 85 == Assign-to as Drop-Down List == 79 86 80 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.87 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. 81 88 82 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]. 89 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 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) 83 94 84 95 == Preset Values for New Tickets == … … 101 112 * '''cc''' - The list of emails for notifying about the ticket change 102 113 103 '''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui'' 114 '''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui''[[BR]] 104 115 105 116 ---- 106 See also: TracGuide, TracWiki, TracTicketsCustomFields, TracNotification 117 See also: TracGuide, TracWiki, TracTicketsCustomFields, TracNotification, TracReports, TracQuery
