Edgewall Software

Changes between Version 7 and Version 8 of 1.3/TracTickets


Ignore:
Timestamp:
Oct 15, 2019, 6:28:13 AM (12 months ago)
Author:
trac
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • 1.3/TracTickets

    v7 v8  
    33[[TranslatedPages]]
    44
    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. 
     5As the central project management element of Trac, tickets can be used for '''project tasks''', '''feature requests''', '''bug reports''' and '''software support issues''', among others.
    66
    77As 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.
     
    1313
    1414A ticket contains the following information:
    15  
     15
    1616 * '''Summary''' — Simple text without WikiFormatting.
    1717 * '''Description''' — The body of the ticket. Accepts WikiFormatting.
    1818 * '''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`.
    2020 * '''Component''' — The project module or subsystem that this ticket concerns.
    2121 * '''Version''' — Version of the project that this ticket pertains to.
     
    4242All edits (field changes, new comments, comment edits) update the "last changed" time of the ticket.
    4343
    44 '''Note:''' 
     44'''Note:'''
    4545 - TracLinks and WikiFormatting can be used in the ticket description and comments. Use TracLinks to refer to other issues, changesets and files.
    4646
     
    5555== Adding Custom Fields
    5656
     57<<<<<<< HEAD
    5758Trac lets you add custom ticket fields. See TracTicketsCustomFields for more information.
     59=======
     60If 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
    5862
    5963== Default Values for Drop-Down Fields
     
    8791'''Notes:'''
    8892 - If you need more flexibility, then use subclass `ConfigurableTicketWorkflow` and override the `get_allowed_owners` method (see [trac:#12807 Trac ticket 12807]).
    89  
     93
    9094 - Activating this option may cause some performance degradation. Read more about this in the [trac:TracPerformance#Configuration Trac performance] page.
    9195
     
    104108 * '''priority''' — The priority dropdown list.
    105109 * '''milestone''' — The milestone dropdown list.
    106  * '''owner''' — The person responsible for the ticket.
    107110 * '''cc''' — The list of emails for notifying about the ticket change.
    108111
    109112Example: `[/newticket?summary=Compile%20Error&version=1.0&component=gui]`
     113
     114To 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
     116For 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.
    110117
    111118== Deleting Tickets #deleter