Changes between Version 1 and Version 2 of TracTickets
- Timestamp:
- 02/08/11 21:48:17 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracTickets
v1 v2 15 15 A ticket contains the following information attributes: 16 16 17 * '''Reporter''' -The author of the ticket.18 * '''Type''' -The nature of the ticket (for example, defect or enhancement request)17 * '''Reporter''' — The author of the ticket. 18 * '''Type''' — The nature of the ticket (for example, defect or enhancement request) 19 19 20 * '''Component''' -The project module or subsystem this ticket concerns.21 * '''Version''' -Version of the project that this ticket pertains to.22 * '''Keywords''' -Keywords that a ticket is marked with. Useful for searching and report generation.20 * '''Component''' — The project module or subsystem this ticket concerns. 21 * '''Version''' — Version of the project that this ticket pertains to. 22 * '''Keywords''' — Keywords that a ticket is marked with. Useful for searching and report generation. 23 23 24 * '''Priority''' -The importance of this issue, ranging from ''trivial'' to ''blocker''.25 * '''Milestone''' -When this issue should be resolved at the latest.26 * '''Assigned to/Owner''' -Principal person responsible for handling the issue.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.''24 * '''Priority''' — The importance of this issue, ranging from ''trivial'' to ''blocker''. 25 * '''Milestone''' — When this issue should be resolved at the latest. 26 * '''Assigned to/Owner''' — Principal person responsible for handling the issue. 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 * '''Resolution''' -Reason for why a ticket was closed. One of {{{fixed}}}, {{{invalid}}}, {{{wontfix}}}, {{{duplicate}}}, {{{worksforme}}}.30 * '''Status''' -What is the current status? One of {{{new}}}, {{{assigned}}}, {{{closed}}}, {{{reopened}}}.31 * '''Summary''' -A brief description summarizing the problem or issue.32 * '''Description''' -The body of the ticket. A good description should be specific, descriptive and to the point.29 * '''Resolution''' — Reason for why a ticket was closed. One of {{{fixed}}}, {{{invalid}}}, {{{wontfix}}}, {{{duplicate}}}, {{{worksforme}}}. 30 * '''Status''' — What is the current status? One of {{{new}}}, {{{assigned}}}, {{{closed}}}, {{{reopened}}}. 31 * '''Summary''' — A brief description summarizing the problem or issue. 32 * '''Description''' — The body of the ticket. A good description should be specific, descriptive and to the point. 33 33 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 [ wiki:TicketTypes type], [wiki:TicketComponent component], version, priority and severity fields can be managed with [wiki:TracAdmin trac-admin] or with the WebAdminplugin.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 37 38 '''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] 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 [[Image(http://trac.edgewall.org/attachment/wiki/TracTickets/Trac%20Ticket%20State%20Chart%2020060603DF.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 == … … 71 69 * `default_type`: Default ticket type 72 70 * `default_version`: Name of the default version 71 * `default_owner`: Name of the default owner, ''if no owner for the component has been set'' 73 72 74 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. 73 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. Some of these can be chosen through the [trac:WebAdmin WebAdmin] plugin in the "Ticket System" section (others in the "trac.ini" section). The default owner for a ticket will be the component owner, if that is set, or `default_owner`, if not. 75 74 76 75 … … 84 83 == Assign-to as Drop-Down List == 85 84 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.85 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 86 88 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]. 87 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]. 88 89 '''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 90 91 '''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) 92 93 '''Note 3:''' Activating this option may cause some performance degradation, read more about this in the [trac:TracPerformance#Configuration Trac performance] page. 89 94 90 95 == Preset Values for New Tickets == … … 94 99 Possible variables are : 95 100 96 * '''type''' -The type droplist97 * '''reporter''' -Name or email of the reporter98 * '''summary''' -Summary line for the ticket99 * '''description''' -Long description of the ticket100 * '''component''' -The component droplist101 * '''version''' -The version droplist102 * '''severity''' -The severity droplist103 * '''keywords''' -The keywords104 * '''priority''' -The priority droplist105 * '''milestone''' -The milestone droplist106 * '''owner''' -The person responsible for the ticket107 * '''cc''' -The list of emails for notifying about the ticket change101 * '''type''' — The type droplist 102 * '''reporter''' — Name or email of the reporter 103 * '''summary''' — Summary line for the ticket 104 * '''description''' — Long description of the ticket 105 * '''component''' — The component droplist 106 * '''version''' — The version droplist 107 * '''severity''' — The severity droplist 108 * '''keywords''' — The keywords 109 * '''priority''' — The priority droplist 110 * '''milestone''' — The milestone droplist 111 * '''owner''' — The person responsible for the ticket 112 * '''cc''' — The list of emails for notifying about the ticket change 108 113 109 114 '''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui''[[BR]]
