Changes between Version 73 and Version 74 of TracTickets
- Timestamp:
- Oct 9, 2015, 9:31:53 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracTickets
v73 v74 1 = The Trac Ticket System =1 = The Trac Ticket System 2 2 [[TracGuideToc]] 3 3 [[TranslatedPages]] … … 14 14 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 WikiStart, or contact your local Trac administrator. 15 15 16 == Ticket Fields ==16 == Ticket Fields 17 17 18 18 A ticket contains the following information: … … 39 39 - Description of the builtin ''priority'' values is available at [trac:TicketTypes#Whyistheseverityfieldgone TicketTypes] 40 40 41 == Changing and Commenting Tickets ==41 == Changing and Commenting Tickets 42 42 43 43 With appropriate permissions, as already mentioned [#edit-permissions above], a ticket entered into Trac can at any time be modified by '''annotating'''. … … 57 57 - See TracWorkflow for information about the state transitions (ticket lifecycle), and how this workflow can be customized. 58 58 59 == Default Values for Drop-Down Fields ==59 == Default Values for Drop-Down Fields 60 60 61 61 The option selected by default for the various drop-down fields can be set in [wiki:TracIni trac.ini], in the `[ticket]` section: … … 72 72 73 73 74 == Hiding Fields and Adding Custom Fields ==74 == Hiding Fields and Adding Custom Fields 75 75 76 76 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''. … … 79 79 80 80 81 == Assign-to as Drop-Down List ==81 == Assign-to as Drop-Down List 82 82 83 83 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 authenticated with the project** and possess the `TICKET_MODIFY` [TracPermissions permissions]. … … 100 100 - Activating this option may cause some performance degradation. Read more about this in the [trac:TracPerformance#Configuration Trac performance] page. 101 101 102 == Preset Values for New Tickets ==102 == Preset Values for New Tickets 103 103 104 104 To create a link to the new-ticket form filled with preset values, you need to call the `/newticket?` URL with `variable=value` separated by `&`. Possible variables are:
