Changes between Version 5 and Version 6 of TracTickets
- Timestamp:
- 07/28/2020 06:19:41 AM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracTickets
v5 v6 36 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. 37 37 38 - Description of the builtin ''priority'' values is available at [trac:T icketTypes#Whyistheseverityfieldgone TicketTypes]38 - Description of the builtin ''priority'' values is available at [trac:TracDev/Proposals/TicketTypes#Whyistheseverityfieldgone TicketTypes]. 39 39 40 40 == 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. 45 45 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.46 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. 47 47 48 48 All edits (field changes, new comments, comment edits) update the "last changed" time of the ticket. … … 98 98 99 99 '''Notes:''' 100 - 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].100 - If you need more flexibility, then use subclass `ConfigurableTicketWorkflow` and override the `get_allowed_owners` method (see [trac:#12807 Trac ticket 12807]). 101 101 102 102 - 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. 117 117 * '''milestone''' — The milestone dropdown list. 118 * '''owner''' — The person responsible for the ticket.119 118 * '''cc''' — The list of emails for notifying about the ticket change. 120 119 121 120 Example: `[/newticket?summary=Compile%20Error&version=1.0&component=gui]` 121 122 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. 123 124 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. 122 125 123 126 == Deleting Tickets