Changes between Version 5 and Version 6 of TracTickets


Ignore:
Timestamp:
Jun 20, 2020, 9:43:52 PM (4 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracTickets

    v5 v6  
    3434 - 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].
    3535
    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.
     36 - The [trac:TicketTypes type], [trac:TicketComponent component], version, priority and severity fields can be managed with [wiki:TracAdmin trac-admin] or through the !WebAdmin.
    3737
    38  - Description of the builtin ''priority'' values is available at [trac:TicketTypes#Whyistheseverityfieldgone TicketTypes]
     38 - Description of the builtin ''priority'' values is available at [trac:TracDev/Proposals/TicketTypes#Whyistheseverityfieldgone TicketTypes].
    3939
    4040== Changing and Commenting Tickets
     
    4444Then, 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.
    4545
    46 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.
     46Comment 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.
    4747
    4848All edits (field changes, new comments, comment edits) update the "last changed" time of the ticket.
     
    6767 * `default_owner`: Name of the default owner. If set to the text `< default >` (the default value), the component owner is used.
    6868
    69 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`.
     69If 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`.
    7070
    7171== Hiding Fields and Adding Custom Fields
     
    116116 * '''priority''' — The priority dropdown list.
    117117 * '''milestone''' — The milestone dropdown list.
    118  * '''owner''' — The person responsible for the ticket.
    119118 * '''cc''' — The list of emails for notifying about the ticket change.
    120119
    121120Example: `[/newticket?summary=Compile%20Error&version=1.0&component=gui]`
    122121
     122To 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.
     123
     124For 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.
     125
     126== Deleting Tickets
     127
     128Ticket 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:
     129{{{#!ini
     130[components]
     131tracopt.ticket.deleter.* = enabled
     132}}}
     133
     134The //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.
     135
    123136----
    124 See also: TracGuide, TracWiki, TracTicketsCustomFields, TracNotification, TracReports, TracQuery
     137See also: TracTicketsCustomFields, TracNotification, TracReports, TracQuery