Changes between Version 3 and Version 4 of TracTickets

Timestamp:

23 Mar 2021, 19:30:37 (4 years ago)

Author:

trac

Comment:

--

TracTickets

@@ -6 +6 @@
 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.
+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.
@@ -19 +19 @@
  * '''Reporter''' — The author of the ticket.
  * '''Type''' — The category of the ticket. The default types are `defect`, `enhancement` and `task`. 
- * '''Component''' — The project module or subsystem this ticket concerns.
+ * '''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 marked with. Useful for searching and report generation.
- * '''Priority''' — The importance of this issue, ranging from ''trivial'' to ''blocker''. A dropdown list if different priorities are defined.
+ * '''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.
  * '''Assigned to/Owner''' — Principal person responsible for handling the issue.
@@ -34 +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 through the !WebAdmin.
 
- - Description of the builtin ''priority'' values is available at [trac:TicketTypes#Whyistheseverityfieldgone TicketTypes]
+ - Description of the builtin ''priority'' values is available at [trac:TracDev/Proposals/TicketTypes#Whyistheseverityfieldgone TicketTypes].
 
 == Changing and Commenting Tickets
@@ -44 +44 @@
 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.
 
-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 (available since Trac version 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.
 
 All edits (field changes, new comments, comment edits) update the "last changed" time of the ticket.
@@ -67 +67 @@
  * `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 can be set 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 !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
@@ -98 +98 @@
 
 '''Notes:'''
- - 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].
+ - If you need more flexibility, then use subclass `ConfigurableTicketWorkflow` and override the `get_allowed_owners` method (see [trac:#12807 Trac ticket 12807]).
  
  - Activating this option may cause some performance degradation. Read more about this in the [trac:TracPerformance#Configuration Trac performance] page.
@@ -116 +116 @@
  * '''priority''' — The priority dropdown list.
  * '''milestone''' — The milestone dropdown list.
- * '''owner''' — The person responsible for the ticket.
  * '''cc''' — The list of emails for notifying about the ticket change.
 
 Example: `[/newticket?summary=Compile%20Error&version=1.0&component=gui]`
 
+To set the ticket owner the workflow action may also need to be selected. For the [TracWorkflow#TicketCreateAction default workflow], the //create and assign// action can be selected with `action=create_and_assign` and the owner specified by assigning `action_create_and_assign_reassign_owner`. Alternatively, you could avoid needing to select the action by using the [TracWorkflow#BasicTicketWorkflowCustomization default attribute] to make //create and assign// the default action.
+
+For other custom workflow actions, determine the variable names by inspecting the `name` attribute of the //action// radio button and the //owner// input or select element.
+
+== Deleting Tickets
+
+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:
+{{{#!ini
+[components]
+tracopt.ticket.deleter.* = enabled
+}}}
+
+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.
+
 ----
-See also: TracGuide, TracWiki, TracTicketsCustomFields, TracNotification, TracReports, TracQuery
+See also: TracTicketsCustomFields, TracNotification, TracReports, TracQuery