| 10 | | An issue is assigned to a person who must resolve it or reassign the ticket to someone else. |
| 11 | | All tickets can be edited, annotated, assigned, prioritized and discussed at any time. |
| | 10 | An issue is assigned to a person who must resolve it or reassign the ticket to someone else. All tickets can be edited, annotated, assigned, prioritized and discussed at any time. |
| | 11 | |
| | 12 | [=#edit-permissions] |
| | 13 | However, a Trac installation may place restrictions on 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. |
| 17 | | * '''Reporter''' - The author of the ticket. |
| 18 | | * '''Type''' - The nature of the ticket (for example, defect or enhancement request) |
| | 19 | * '''Reporter''' — The author of the ticket. |
| | 20 | * '''Type''' — The category of the ticket. The default types are `defect`, `enhancement` and `task`. |
| | 21 | * '''Component''' — The project module or subsystem this ticket concerns. |
| | 22 | * '''Version''' — Version of the project that this ticket pertains to. |
| | 23 | * '''Keywords''' — Keywords that a ticket is marked with. Useful for searching and report generation. |
| | 24 | * '''Priority''' — The importance of this issue, ranging from ''trivial'' to ''blocker''. A pull-down if different priorities are defined. |
| | 25 | * '''Milestone''' — Due date of when this issue should be resolved. A pull-down menu containing a list of milestones. |
| | 26 | * '''Assigned to/Owner''' — Principal person responsible for handling the issue. |
| | 27 | * '''Cc''' — A comma-separated list of other users or email addresses to notify. ''Note that this does not imply responsibility or any other policy.'' |
| | 28 | * '''Resolution''' — Reason for why a ticket was closed. One of {{{fixed}}}, {{{invalid}}}, {{{wontfix}}}, {{{duplicate}}}, {{{worksforme}}}. |
| | 29 | * '''Status''' — What is the current status? The statuses are defined in the [TracWorkflow#BasicTicketWorkflowCustomization ticket workflow]. For the default workflow the statuses are `new`, `assigned`, `accepted`, `closed` and `reopened`. |
| | 30 | * '''Summary''' — A description summarizing the issue. Simple text without WikiFormatting. |
| | 31 | * '''Description''' — The body of the ticket. A good description should be specific, descriptive and to the point. Accepts WikiFormatting. |
| 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. |
| | 36 | - 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. |
| 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 | | |
| 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] |
| | 38 | - Description of the builtin ''priority'' values is available at [trac:TicketTypes#Whyistheseverityfieldgone TicketTypes] |
| 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. |
| | 70 | 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 can be set in the [[wiki:TracIni#ticket-section|"[ticket]"]] section in `trac.ini`. |
| 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]. |
| | 84 | To appear in the dropdown list, a user needs be registered with the project, ie 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]. |
| 99 | | Possible variables are : |
| | 97 | * '''type''' — The type droplist |
| | 98 | * '''reporter''' — Name or email of the reporter |
| | 99 | * '''summary''' — Summary line for the ticket |
| | 100 | * '''description''' — Long description of the ticket |
| | 101 | * '''component''' — The component droplist |
| | 102 | * '''version''' — The version droplist |
| | 103 | * '''severity''' — The severity droplist |
| | 104 | * '''keywords''' — The keywords |
| | 105 | * '''priority''' — The priority droplist |
| | 106 | * '''milestone''' — The milestone droplist |
| | 107 | * '''owner''' — The person responsible for the ticket |
| | 108 | * '''cc''' — The list of emails for notifying about the ticket change |
| 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]] |
| | 110 | Example: ''`[/newticket?summary=Compile%20Error&version=1.0&component=gui]`'' |
