Changes between Version 7 and Version 8 of 1.3/TracTickets
- Timestamp:
- Oct 15, 2019, 6:28:13 AM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
1.3/TracTickets
v7 v8 3 3 [[TranslatedPages]] 4 4 5 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. 5 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. 6 6 7 7 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. … … 13 13 14 14 A ticket contains the following information: 15 15 16 16 * '''Summary''' — Simple text without WikiFormatting. 17 17 * '''Description''' — The body of the ticket. Accepts WikiFormatting. 18 18 * '''Reporter''' — The author of the ticket. 19 * '''Type''' — The default types are `defect`, `enhancement` and `task`. 19 * '''Type''' — The default types are `defect`, `enhancement` and `task`. 20 20 * '''Component''' — The project module or subsystem that this ticket concerns. 21 21 * '''Version''' — Version of the project that this ticket pertains to. … … 42 42 All edits (field changes, new comments, comment edits) update the "last changed" time of the ticket. 43 43 44 '''Note:''' 44 '''Note:''' 45 45 - TracLinks and WikiFormatting can be used in the ticket description and comments. Use TracLinks to refer to other issues, changesets and files. 46 46 … … 55 55 == Adding Custom Fields 56 56 57 <<<<<<< HEAD 57 58 Trac lets you add custom ticket fields. See TracTicketsCustomFields for more information. 59 ======= 60 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`. 61 >>>>>>> 1.2 58 62 59 63 == Default Values for Drop-Down Fields … … 87 91 '''Notes:''' 88 92 - If you need more flexibility, then use subclass `ConfigurableTicketWorkflow` and override the `get_allowed_owners` method (see [trac:#12807 Trac ticket 12807]). 89 93 90 94 - Activating this option may cause some performance degradation. Read more about this in the [trac:TracPerformance#Configuration Trac performance] page. 91 95 … … 104 108 * '''priority''' — The priority dropdown list. 105 109 * '''milestone''' — The milestone dropdown list. 106 * '''owner''' — The person responsible for the ticket.107 110 * '''cc''' — The list of emails for notifying about the ticket change. 108 111 109 112 Example: `[/newticket?summary=Compile%20Error&version=1.0&component=gui]` 113 114 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. 115 116 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. 110 117 111 118 == Deleting Tickets #deleter
