| 13 | | == Ticket Fields == |
| | 13 | A ticket contains the following information: |
| | 14 | |
| | 15 | * '''Summary''' — Simple text without WikiFormatting. |
| | 16 | * '''Description''' — The body of the ticket. Accepts WikiFormatting. |
| | 17 | * '''Reporter''' — The author of the ticket. |
| | 18 | * '''Type''' — The default types are `defect`, `enhancement` and `task`. |
| | 19 | * '''Component''' — The project module or subsystem that this ticket concerns. |
| | 20 | * '''Version''' — Version of the project that this ticket pertains to. |
| | 21 | * '''Keywords''' — Useful for searching and report generation. |
| | 22 | * '''Priority''' — The default priorities are `trivial`, `minor`, `major`, `critical` and `blocker`. A dropdown list when multiple priorities are defined. |
| | 23 | * '''Severity''' — Similar to Priority, but the distinction may be useful for some projects. No severities are defined by default, therefore the field will be hidden from the ticket form. |
| | 24 | * '''Milestone''' — Milestone in which the ticket will be resolved. A dropdown list. |
| | 25 | * '''Assigned to/Owner''' — Principal person responsible for handling the issue. |
| | 26 | * '''Cc''' — A comma-separated list of other users or email addresses to notify when changes are made to a ticket. |
| | 27 | * '''Resolution''' — Reason why a ticket was closed. Default values are `fixed`, `invalid`, `wontfix`, `duplicate`, `worksforme`. |
| | 28 | * '''Status''' — The statuses are defined in the [TracWorkflow#BasicTicketWorkflowCustomization ticket workflow]. For the default workflow the statuses are `new`, `assigned`, `accepted`, `closed` and `reopened`. |
| 15 | | A ticket contains the following information attributes: |
| | 30 | '''Notes:''' |
| | 31 | - The type, [trac:TicketComponent component], [TracRoadmap milestone], version, priority, severity fields and resolution can be managed using [TracAdmin trac-admin] or !WebAdmin. |
| | 32 | |
| | 33 | == Changing and Commenting Tickets |
| | 34 | |
| | 35 | With appropriate permissions, tickets can be commented and ticket properties changed. When viewing a ticket, the history of changes will appear below the ticket properties box. |
| | 36 | |
| | 37 | By default an authenticated user can edit their own ticket comments. Users with `TICKET_EDIT_COMMENT` can edit any comment. |
| | 38 | |
| | 39 | Comment editing is meant for making small corrections to comments, like fixing formatting or spelling errors. For major edits, you should be adding a new comment instead. Editing a comment will not produce a new entry on [/timeline], while entering a new comment or other changes will do. |
| | 40 | |
| | 41 | All edits (field changes, new comments, comment edits) update the "last changed" time of the ticket. |
| | 42 | |
| | 43 | '''Note:''' |
| | 44 | - TracLinks and WikiFormatting can be used in the ticket description and comments. Use TracLinks to refer to other issues, changesets and files. |
| | 45 | |
| | 46 | - See TracNotification for how to configure email notifications on ticket changes. |
| | 47 | |
| | 48 | - See TracWorkflow for information about the state transitions (ticket lifecycle), and customization of the workflow. |
| | 49 | |
| | 50 | == Hiding Fields |
| | 51 | |
| | 52 | Many of the default ticket fields can be hidden from the ticket web interface by removing all the possible values through the !WebAdmin or using [TracAdmin trac-admin]. This only applies to drop-down lists: ''type'', ''priority'', ''severity'', ''component'', ''version'' and ''milestone''. |
| | 53 | |
| | 54 | == Adding Custom Fields |
| | 55 | |
| | 56 | Trac lets you add custom ticket fields. See TracTicketsCustomFields for more information. |
| | 57 | |
| | 58 | == Default Values for Drop-Down Fields |
| | 59 | |
| | 60 | The option selected by default for the various drop-down fields can be set in [TracIni trac.ini]. Refer to the values prefixed with `default_` in the [[TracIni#ticket-section|"[ticket]"]] section. The default value of several fields can also be set through the !WebAdmin. |
| | 61 | |
| | 62 | If any of these options are omitted, the default value will either be the first in the list, or an empty value when allowed. The [[TracIni#ticket-allowed_empty_fields-option|allowed_empty_fields]] option determines which fields may have an empty value. |
| | 63 | |
| | 64 | == Assign-to as Drop-Down List |
| | 65 | |
| | 66 | 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 [TracIni trac.ini] to `true`. In that case, Trac will populate the list with all users who **have an authenticated session** and possess the `TICKET_MODIFY` [TracPermissions permissions]. |
| | 67 | |
| | 68 | An authenticated session will be created the first time a user authenticates with the project. You can manually add an authenticated session using the ["TracAdmin#?session add" trac-admin] `session add` command. The `:1` suffix on the session id (i.e. username) is the key to creating an authenticated session: |
| | 69 | {{{#!sh |
| | 70 | trac-admin /path/to/projenv session add <sid>:1 [name] [email] |
| | 71 | }}} |
| | 72 | |
| | 73 | You may find the dropdown list is //overpopulated// with users that are no longer active in the project. Revoking authentication privileges will not remove the session data that is used to populate the dropdown list. The [TracAdmin trac-admin] command can be used to list and remove sessions: |
| | 74 | |
| | 75 | - List all sessions: |
| | 76 | {{{#!sh |
| | 77 | trac-admin /path/to/projenv session list |
| | 78 | }}} |
| | 79 | - Remove a session: |
| | 80 | {{{#!sh |
| | 81 | trac-admin /path/to/projenv session delete SID |
| | 82 | }}} |
| | 83 | |
| | 84 | Alternatively, you can just revoke `TICKET_MODIFY` from users that you don't want to be included in the list. However, that will not be possible if you've granted `TICKET_MODIFY` to all //anonymous// or //authenticated// users. |
| | 85 | |
| | 86 | '''Notes:''' |
| | 87 | - If you need more flexibility, you can subclass `ConfigurableTicketWokflow` and override the `get_allowed_owners` method. |
| 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 | | |
| 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. |
| | 93 | 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 `&`. Possible variables are: |
| 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]. |
| | 95 | * '''type''' — The type droplist. |
| | 96 | * '''reporter''' — Name or email of the reporter. |
| | 97 | * '''summary''' — Summary line for the ticket. |
| | 98 | * '''description''' — Long description of the ticket. |
| | 99 | * '''component''' — The component dropdown list. |
| | 100 | * '''version''' — The version dropdown list. |
| | 101 | * '''severity''' — The severity dropdown list. |
| | 102 | * '''keywords''' — The keywords or tags. |
| | 103 | * '''priority''' — The priority dropdown list. |
| | 104 | * '''milestone''' — The milestone dropdown list. |
| | 105 | * '''owner''' — The person responsible for the ticket. |
| | 106 | * '''cc''' — The list of emails for notifying about the ticket change. |
| 57 | | '''Note:''' See TracNotification for how to configure email notifications of ticket changes. |
| 58 | | |
| 59 | | '''Note:''' See TracWorkflow for information about the state transitions (ticket lifecycle), and how this workflow can be customized. |
| 60 | | |
| 61 | | == Default Values for Drop-Down Fields == |
| 62 | | |
| 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 | | * `default_component`: Name of the component selected by default |
| 66 | | * `default_milestone`: Name of the default milestone |
| 67 | | * `default_priority`: Default priority value |
| 68 | | * `default_severity`: Default severity value |
| 69 | | * `default_type`: Default ticket type |
| 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'' |
| 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. 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. |
| 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 accessed the project to populate the drop-down field. |
| 86 | | |
| 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. |
| 94 | | |
| 95 | | == Preset Values for New Tickets == |
| 96 | | |
| 97 | | 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 &. |
| 98 | | |
| 99 | | Possible variables are : |
| 100 | | |
| 101 | | * '''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 |
| 113 | | |
| 114 | | '''Example:''' ''/trac/newticket?summary=Compile%20Error&version=1.0&component=gui''[[BR]] |
| | 130 | The //Clone// buttons appears next to the //Reply// buttons in the ticket description and ticket change areas. The ticket summary, description and properties are cloned, with minor modifications such as changing the ticket reporter to the currently authenticated user. |
