Changes between Version 6 and Version 7 of TracTickets

Timestamp:

Apr 24, 2015, 5:15:04 PM (10 years ago)

Author:

trac

Comment:

--

TracTickets

@@ -2 +2 @@
 [[TracGuideToc]]
 
-The Trac ticket database provides simple but effective tracking of issues and bugs within a project.
+The Trac ticket database provides simple but effective way to track issues and software bugs within a project.
 
 As the central project management element of Trac, tickets can be used for '''project tasks''', '''feature requests''', '''bug reports''', '''software support issues''' among others. 
 
-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, suggest improvements and discuss resolutions.
+As with the TracWiki, this subsystem has been designed with the goal of making user contribution and participation as simple as possible.
 
-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.
+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.
 
 [=#edit-permissions]
-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.
+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.
 
 == Ticket Fields ==
 
-A  ticket contains the following information attributes:
+A ticket contains the following information:
  
  * '''Reporter''' — The author of the ticket.
- * '''Type''' — The nature of the ticket (for example, defect or enhancement request). See TicketTypes for more details.
+ * '''Type''' — The category of the ticket. The default types are `defect`,  `enhancement` and `task`. 
  * '''Component''' — The project module or subsystem this ticket concerns.
  * '''Version''' — Version of the project that this ticket pertains to.
  * '''Keywords''' — Keywords that a ticket is marked with. Useful for searching and report generation.
- * '''Priority''' — The importance of this issue, ranging from ''trivial'' to ''blocker''. A pull-down if different priorities where defined.
- * '''Milestone''' — When this issue should be resolved at the latest. A pull-down menu containing a list of milestones.
+ * '''Priority''' — The importance of this issue, ranging from ''trivial'' to ''blocker''. A pull-down if different priorities are defined.
+ * '''Milestone''' — Due date of when this issue should be resolved. A pull-down menu containing a list of milestones.
  * '''Assigned to/Owner''' — Principal person responsible for handling the issue.
- * '''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.''
+ * '''Cc''' — A comma-separated list of other users or email addresses to notify. ''Note that this does not imply responsibility or any other policy.''
  * '''Resolution''' — Reason for why a ticket was closed. One of {{{fixed}}}, {{{invalid}}}, {{{wontfix}}}, {{{duplicate}}}, {{{worksforme}}}.
- * '''Status''' — What is the current status? One of {{{new}}}, {{{assigned}}}, {{{accepted}}}, {{{closed}}}, {{{reopened}}}.
- * '''Summary''' — A brief description summarizing the problem or issue. Simple text without WikiFormatting.
+ * '''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`.
+ * '''Summary''' — A description summarizing the issue. Simple text without WikiFormatting.
  * '''Description''' — The body of the ticket. A good description should be specific, descriptive and to the point. Accepts WikiFormatting.
 
@@ -35 +34 @@
  - 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].
 
- - 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.
+ - 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.
 
  - Description of the builtin ''priority'' values is available at [trac:TicketTypes#Whyistheseverityfieldgone TicketTypes]
@@ -67 +66 @@
  * `default_type`: Default ticket type
  * `default_version`: Name of the default version
- * `default_owner`: Name of the default owner. If set to the text "< default >" (the default value), the component owner is used.
+ * `default_owner`: Name of the default owner. If set to the text `< default >` (the default value), the component owner is used.
 
-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 [[wiki:TracIni#ticket-section|"[ticket]"]] section in `trac.ini`).
+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`.
 
 
@@ -83 +82 @@
 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.
 
-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].
+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].
 
 '''Notes:''' 
- - 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
+ - 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.
 
- - 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)
+ - 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].
 
- -  Activating this option may cause some performance degradation, read more about this in the [trac:TracPerformance#Configuration Trac performance] page.
+ -  Activating this option may cause some performance degradation. Read more about this in the [trac:TracPerformance#Configuration Trac performance] page.
 
 == Preset Values for New Tickets ==
 
-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 :
+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:
 
  * '''type''' — The type droplist
@@ -111 +108 @@
  * '''cc''' — The list of emails for notifying about the ticket change
 
-Example: ''`[/newticket?summary=Compile%20Error&version=1.0&component=gui]`''[[BR]]
+Example: ''`[/newticket?summary=Compile%20Error&version=1.0&component=gui]`''
 
 ----