Changes between Version 4 and Version 5 of TracTickets

Timestamp:

2020-07-23T14:06:24-07:00 (4 years ago)

Author:

trac

Comment:

--

TracTickets

@@ -2 +2 @@
 [[TracGuideToc]]
 
-The Trac ticket system provides a 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''' and '''software support issues''', among others. 
 
-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 to make 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.
+As with the TracWiki, this subsystem has been designed to make user contribution and participation as simple as possible. Tickets can be edited, annotated, assigned, prioritized and discussed.
 
 [=#edit-permissions]
-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 of WikiStart, or contact your local Trac administrator.
+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, or contact your local Trac administrator.
 
 == Ticket Fields
@@ -17 +13 @@
 A ticket contains the following information:
  
+ * '''Summary''' — Simple text without WikiFormatting.
+ * '''Description''' — The body of the ticket. Accepts WikiFormatting.
  * '''Reporter''' — The author of the ticket.
- * '''Type''' — The category of the ticket. The default types are `defect`, `enhancement` and `task`. 
+ * '''Type''' — The default types are `defect`, `enhancement` and `task`. 
  * '''Component''' — The project module or subsystem that this ticket concerns.
  * '''Version''' — Version of the project that this ticket pertains to.
- * '''Keywords''' — Keywords that a ticket is tagged with. Useful for searching and report generation.
- * '''Priority''' — The importance of this issue, ranging from ''trivial'' to ''blocker''. A dropdown list when multiple priorities are defined.
- * '''Milestone''' — Due date of when this issue should be resolved. A dropdown list containing the milestones.
+ * '''Keywords''' — Useful for searching and report generation.
+ * '''Priority''' — The default priorities are `trivial`, `minor`, `major`, `critical` and `blocker`. A dropdown list when multiple priorities are defined.
+ * '''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.
+ * '''Milestone''' — Milestone in which the ticket will be resolved. A dropdown list.
  * '''Assigned to/Owner''' — Principal person responsible for handling the issue.
- * '''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? 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.
+ * '''Cc''' — A comma-separated list of other users or email addresses to notify when changes are made to a ticket.
+ * '''Resolution''' — Reason why a ticket was closed. Default values are `fixed`, `invalid`, `wontfix`, `duplicate`, `worksforme`.
+ * '''Status''' — The statuses are defined in the [TracWorkflow#BasicTicketWorkflowCustomization ticket workflow]. For the default workflow the statuses are `new`, `assigned`, `accepted`, `closed` and `reopened`.
 
-'''Notes:''' 
- - 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 through the !WebAdmin.
-
- - Description of the builtin ''priority'' values is available at [trac:TicketTypes#Whyistheseverityfieldgone TicketTypes]
+'''Notes:'''
+ - The type, [trac:TicketComponent component], [TracRoadmap milestone], version, priority, severity fields and resolution can be managed using [TracAdmin trac-admin] or !WebAdmin.
 
 == Changing and Commenting Tickets
 
-With appropriate permissions, as already mentioned [#edit-permissions above], a ticket entered into Trac can at any time be modified by '''annotating'''.
+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.
 
-Then, annotations like changes and comments to the ticket are logged as a part of the ticket itself. When viewing a ticket, the history of changes will appear below the main ticket area.
+By default an authenticated user can edit their own ticket comments. Users with `TICKET_EDIT_COMMENT` can edit any comment.
 
-Comment editing (available since 0.12) is meant to be used to make small corrections to comments, like fixing formatting, forgotten WikiFormatting or spelling errors, not major edits. For longer 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.
+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.
 
 All edits (field changes, new comments, comment edits) update the "last changed" time of the ticket.
 
-'''Notes:''' 
- - An important feature is being able to use TracLinks and WikiFormatting in ticket descriptions and comments. Use TracLinks to refer to other issues, changesets or files to make your ticket more specific and easier to understand.
+'''Note:''' 
+ - TracLinks and WikiFormatting can be used in the ticket description and comments. Use TracLinks to refer to other issues, changesets and files.
 
- - See TracNotification for how to configure email notifications of ticket changes.
+ - See TracNotification for how to configure email notifications on ticket changes.
 
- - See TracWorkflow for information about the state transitions (ticket lifecycle), and how this workflow can be customized.
+ - See TracWorkflow for information about the state transitions (ticket lifecycle), and customization of the workflow.
+
+== Hiding Fields
+
+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''.
+
+== Adding Custom Fields
+
+Trac lets you add custom ticket fields. See TracTicketsCustomFields for more information.
 
 == Default Values for Drop-Down Fields
 
-The option selected by default for the various drop-down fields can be set in [wiki:TracIni trac.ini], in the `[ticket]` section:
+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.
 
- * `default_component`: Name of the component selected by default.
- * `default_milestone`: Name of the default milestone.
- * `default_priority`: Default priority value.
- * `default_severity`: Default severity value.
- * `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.
-
-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 !WebAdmin in the "Ticket System" section, others can be set in the [[wiki:TracIni#ticket-section|"[ticket]"]] section in `trac.ini`.
-
-== Hiding Fields and Adding Custom Fields
-
-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''.
-
-Trac also lets you add your own custom ticket fields. See TracTicketsCustomFields for more information.
+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.
 
 == Assign-to as Drop-Down List
 
-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 populate the list with all users who **have an authenticated session** and possess the `TICKET_MODIFY` [TracPermissions permissions].
+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].
 
 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:
@@ -84 +71 @@
 }}}
 
-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 [wiki:TracAdmin trac-admin] command can be used to list and remove sessions:
+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:
 
  - List all sessions:
@@ -98 +85 @@
 
 '''Notes:'''
- - If you need more flexibility and aren't afraid of a little plugin coding of your own, see the [https://trac-hacks.org/wiki/FlexibleAssignToPlugin FlexibleAssignTo plugin].
+ - If you need more flexibility, you can subclass `ConfigurableTicketWokflow` and override the `get_allowed_owners` method.
  
  - Activating this option may cause some performance degradation. Read more about this in the [trac:TracPerformance#Configuration Trac performance] page.
@@ -121 +108 @@
 Example: `[/newticket?summary=Compile%20Error&version=1.0&component=gui]`
 
-== Deleting Tickets
+== Deleting Tickets #deleter
 
 Ticket delete and ticket change delete functions are enabled through an optional component. To enable the functionality edit the [TracIni#components-section "[components]"] section of TracIni:
@@ -131 +118 @@
 The //Delete// buttons appears next to the //Reply// buttons in the ticket description and ticket change areas. `TICKET_ADMIN` permission is required for deleting tickets and ticket changes.
 
+Tickets and ticket changes can also be deleted using the TracAdmin `ticket remove` and `ticket remove_comment` commands.
+
+== Cloning Tickets #cloner
+
+The ticket clone function is enabled through an optional component. To enable the functionality edit the [TracIni#components-section "[components]"] section of TracIni:
+{{{#!ini
+[components]
+tracopt.ticket.clone.* = enabled
+}}}
+
+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.
+
 ----
-See also: TracTicketsCustomFields, TracNotification, TracReports, TracQuery
+See also: TracTicketsCustomFields, TracNotification, TracReports, TracQuery, TracRepositoryAdmin#CommitTicketUpdater