Changes between Version 1 and Version 2 of TracTickets
- Timestamp:
- Jan 30, 2006, 11:09:12 PM (19 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracTickets
v1 v2 18 18 19 19 * '''Reporter''' - The author of the ticket. 20 * '''Type''' - The nature of the ticket (for example, defect or enhancement request) 20 21 21 22 * '''Component''' - The project module or subsystem this ticket concerns. 22 23 * '''Version''' - Version of the project that this ticket pertains to. 23 * '''Severity''' - What are the effects the issue described? Ranges from an ''enhancement'' request to ''blocker'' (must be fixed before next milestone).24 24 * '''Keywords''' - Keywords that a ticket is marked with. Useful for searching and report generation. 25 25 26 * '''Priority''' - The importance of is the issue relative to other tasks.26 * '''Priority''' - The importance of this issue, ranging from ''trivial'' to ''blocker''. 27 27 * '''Milestone''' - When this issue should be resolved at the latest. 28 * '''Assigned to ''' - Principal person responsible for handling the issue.29 * '''Cc''' - A list of other associated people. '' note: this does '''not''' imply responsiblity or any other policy.28 * '''Assigned to/Owner''' - Principal person responsible for handling the issue. 29 * '''Cc''' - A list of other associated people. ''Note that this does not imply responsiblity or any other policy.'' 30 30 31 * '''Resolution''' - Reason for why a ticket was closed , such as {{{fixed}}}, {{{invalid}}}, {{{duplicate}}}, etc.32 * '''Status''' - What is the current status? (One of {{{new}}}, {{{assigned}}}, {{{closed}}}, {{{reopened}}}.)31 * '''Resolution''' - Reason for why a ticket was closed. One of {{{fixed}}}, {{{invalid}}}, {{{wontfix}}}, {{{duplicate}}}, {{{worksforme}}}. 32 * '''Status''' - What is the current status? One of {{{new}}}, {{{assigned}}}, {{{closed}}}, {{{reopened}}}. 33 33 * '''Summary''' - A brief description summarizing the problem or issue. 34 * '''Description''' - The body of the ticket. A good description should be '''specific, descriptive and to the point'''. 34 * '''Description''' - The body of the ticket. A good description should be specific, descriptive and to the point. 35 36 '''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]. 37 35 38 36 39 == Changing and Commenting Tickets == … … 40 43 the ticket are logged as a part of the ticket itself. 41 44 42 When viewing a ticket, th is logof changes will appear below the main ticket area.45 When viewing a ticket, the history of changes will appear below the main ticket area. 43 46 44 ''In the Trac project, we use ticket comments to discuss issues and 45 tasks. This makes understanding the motivation behind a design- or implementation choice easier, when returning to it later.'' 47 ''In the Trac project, we use ticket comments to discuss issues and tasks. This makes 48 understanding the motivation behind a design- or implementation choice easier, 49 when returning to it later.'' 46 50 47 51 '''Note:''' An important feature is being able to use TracLinks and … … 55 59 http://projects.edgewall.com/trac/attachment/wiki/TracTickets/Trac%20Ticket%20State%20Chart%2020040607DF.png?format=raw 56 60 57 == Advanced: Preset values for New Tickets from URL ==58 61 59 To create a link to the new-ticket form filled with preset values, you need to call the /newticket? URL with variable=value separated by &. 62 == Default Values for Drop-Down Fields == 63 64 The option selected by default for the various drop-down fields can be set in [wiki:TracIni trac.ini], in the `[ticket]` section: 65 66 * `default_type`: Default ticket type 67 * `default_component`: Name of the component selected by default 68 * `default_version`: Name of the default version 69 * `default_milestone`: Name of the default milestone 70 * `default_priority`: Default priority value 71 * `default_severity`: Default severity value 72 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. 74 75 76 == Hiding Fields and Adding Custom Fields == 77 78 Many of the default ticket fields can be hidden from the ticket web interface simply by removing all the possible values through [wiki:TracAdmin trac-admin]. This of course only applies to drop-down fields, such as ''type'', ''priority'', ''severity'', ''component'', ''version'' and ''milestone''. 79 80 Trac also lets you add your own custom ticket fields. See TracTicketsCustomFields for more information. 81 82 83 == Assign-to as Drop-Down List == 84 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 logged in and set their email address to populate the drop-down field. 86 87 ''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.'' 88 89 90 == Preset Values for New Tickets == 91 92 To create a link to the new-ticket form filled with preset values, you need to call the `/newticket?` URL with variable=value separated by &. 60 93 61 94 Possible variables are :
