Changes between Version 55 and Version 56 of TracTickets
- Timestamp:
- Mar 1, 2011, 8:05:35 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracTickets
v55 v56 5 5 The Trac ticket database provides simple but effective tracking of issues and bugs within a project. 6 6 7 As the central project management element of Trac, tickets are used for '''project tasks''', '''feature requests''', '''bug reports''' and '''software support issues'''.7 As the central project management element of Trac, tickets can be used for '''project tasks''', '''feature requests''', '''bug reports''' and '''software support issues'''. 8 8 9 9 As with the TracWiki, this subsystem has been designed with the goal of making user contribution and participation as simple as possible. It should be as easy as possible to report bugs, ask questions and suggest improvements. … … 11 11 An issue is assigned to a person who must resolve it or reassign the ticket to someone else. 12 12 All tickets can be edited, annotated, assigned, prioritized and discussed at any time. 13 14 [=#edit-permissions] 15 However, some Trac installations may put restrictions in place about who can change what. For example, the default installation doesn't permit to non-authenticated users ("anonymous" users) to change anything, even to comment on an issue, for obvious spam prevention reasons. Check the local contributing policy, which you can usually find on the front page WikiStart, or contact your local Trac administrator. 13 16 14 17 == Ticket Fields == … … 33 36 * '''Description''' — The body of the ticket. A good description should be specific, descriptive and to the point. 34 37 35 '''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 '''Notes:''' 39 - 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]. 36 40 37 '''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.41 - 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. 38 42 39 '''Note:'''Description of the builtin ''priority'' values is available at [trac:TicketTypes#Whyistheseverityfieldgone TicketTypes]43 - Description of the builtin ''priority'' values is available at [trac:TicketTypes#Whyistheseverityfieldgone TicketTypes] 40 44 41 45 == Changing and Commenting Tickets == … … 43 47 Once a ticket has been entered into Trac, you can at any time change the 44 48 information by '''annotating''' the bug. This means changes and comments to 45 the ticket are logged as a part of the ticket itself. 49 the ticket are logged as a part of the ticket itself. 50 As already mentioned [#edit-permissions above], you'll however need the appropriate permissions for doing so. 46 51 47 52 When viewing a ticket, the history of changes will appear below the main ticket area. … … 51 56 when returning to it later.'' 52 57 53 '''Note:''' An important feature is being able to use TracLinks and 54 WikiFormatting in ticket descriptions and comments. Use TracLinks to refer to 55 other issues, changesets or files to make your ticket more specific and easier 56 to understand. 58 '''Notes:''' 59 - An important feature is being able to use TracLinks and 60 WikiFormatting in ticket descriptions and comments. Use TracLinks to refer to 61 other issues, changesets or files to make your ticket more specific and easier 62 to understand. 57 63 58 '''Note:'''See TracNotification for how to configure email notifications of ticket changes.64 - See TracNotification for how to configure email notifications of ticket changes. 59 65 60 '''Note:'''See TracWorkflow for information about the state transitions (ticket lifecycle), and how this workflow can be customized.66 - See TracWorkflow for information about the state transitions (ticket lifecycle), and how this workflow can be customized. 61 67 62 68 == Default Values for Drop-Down Fields == … … 88 94 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]. 89 95 90 '''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 96 '''Notes:''' 97 - 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 91 98 92 '''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)99 - 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) 93 100 94 '''Note 3:'''Activating this option may cause some performance degradation, read more about this in the [trac:TracPerformance#Configuration Trac performance] page.101 - Activating this option may cause some performance degradation, read more about this in the [trac:TracPerformance#Configuration Trac performance] page. 95 102 96 103 == Preset Values for New Tickets == 97 104 98 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 &.105 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 `&`. 99 106 100 107 Possible variables are : … … 113 120 * '''cc''' — The list of emails for notifying about the ticket change 114 121 115 '''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui''[[BR]]122 Example: ''`[/newticket?summary=Compile%20Error&version=1.0&component=gui]`''[[BR]] 116 123 117 124 ----
