Changes between Version 2 and Version 3 of TracTickets


Ignore:
Timestamp:
2019-05-02T09:45:05-03:00 (5 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracTickets

    v2 v3  
    1 = The Trac Ticket System
     1= The Trac Ticket System =
    22[[TracGuideToc]]
    33
    4 The Trac ticket system provides a simple but effective way to track issues and software bugs within a project.
     4The Trac ticket database provides simple but effective way to track issues and software bugs within a project.
    55
    66As the central project management element of Trac, tickets can be used for '''project tasks''', '''feature requests''', '''bug reports''', '''software support issues''' among others.
    77
    8 As with the TracWiki, this subsystem has been designed to make user contribution and participation as simple as possible.
     8As with the TracWiki, this subsystem has been designed with the goal of making user contribution and participation as simple as possible.
    99
    1010An issue is assigned to a person who must resolve it or reassign the ticket to someone else. All tickets can be edited, annotated, assigned, prioritized and discussed at any time.
    1111
    1212[=#edit-permissions]
    13 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 of WikiStart, or contact your local Trac administrator.
     13However, 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.
    1414
    15 == Ticket Fields
     15== Ticket Fields ==
    1616
    1717A ticket contains the following information:
    1818 
    1919 * '''Reporter''' — The author of the ticket.
    20  * '''Type''' — The category of the ticket. The default types are `defect`, `enhancement` and `task`.
    21  * '''Component''' — The project module or subsystem that this ticket concerns.
     20 * '''Type''' — The category of the ticket. The default types are `defect`,  `enhancement` and `task`.
     21 * '''Component''' — The project module or subsystem this ticket concerns.
    2222 * '''Version''' — Version of the project that this ticket pertains to.
    23  * '''Keywords''' — Keywords that a ticket is tagged with. Useful for searching and report generation.
    24  * '''Priority''' — The importance of this issue, ranging from ''trivial'' to ''blocker''. A dropdown list when multiple priorities are defined.
    25  * '''Milestone''' — Due date of when this issue should be resolved. A dropdown list containing the milestones.
     23 * '''Keywords''' — Keywords that a ticket is marked with. Useful for searching and report generation.
     24 * '''Priority''' — The importance of this issue, ranging from ''trivial'' to ''blocker''. A pull-down if different priorities are defined.
     25 * '''Milestone''' — Due date of when this issue should be resolved. A pull-down menu containing a list of milestones.
    2626 * '''Assigned to/Owner''' — Principal person responsible for handling the issue.
    27  * '''Cc''' — A comma-separated list of other users or email addresses to notify. Note that this does not imply responsibility or any other policy.
     27 * '''Cc''' — A comma-separated list of other users or email addresses to notify. ''Note that this does not imply responsibility or any other policy.''
    2828 * '''Resolution''' — Reason for why a ticket was closed. One of {{{fixed}}}, {{{invalid}}}, {{{wontfix}}}, {{{duplicate}}}, {{{worksforme}}}.
    2929 * '''Status''' — What is the current status? The statuses are defined in the [TracWorkflow#BasicTicketWorkflowCustomization ticket workflow]. For the default workflow the statuses are `new`, `assigned`, `accepted`, `closed` and `reopened`.
    … …  
    3838 - Description of the builtin ''priority'' values is available at [trac:TicketTypes#Whyistheseverityfieldgone TicketTypes]
    3939
    40 == Changing and Commenting Tickets
     40== Changing and Commenting Tickets ==
    4141
    4242With appropriate permissions, as already mentioned [#edit-permissions above], a ticket entered into Trac can at any time be modified by '''annotating'''.
    … …  
    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 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.
     49
    4950
    5051'''Notes:'''
    … …  
    5556 - See TracWorkflow for information about the state transitions (ticket lifecycle), and how this workflow can be customized.
    5657
    57 == Default Values for Drop-Down Fields
     58== Default Values for Drop-Down Fields ==
    5859
    5960The option selected by default for the various drop-down fields can be set in [wiki:TracIni trac.ini], in the `[ticket]` section:
    6061
    61  * `default_component`: Name of the component selected by default.
    62  * `default_milestone`: Name of the default milestone.
    63  * `default_priority`: Default priority value.
    64  * `default_severity`: Default severity value.
    65  * `default_type`: Default ticket type.
    66  * `default_version`: Name of the default version.
     62 * `default_component`: Name of the component selected by default
     63 * `default_milestone`: Name of the default milestone
     64 * `default_priority`: Default priority value
     65 * `default_severity`: Default severity value
     66 * `default_type`: Default ticket type
     67 * `default_version`: Name of the default version
    6768 * `default_owner`: Name of the default owner. If set to the text `< default >` (the default value), the component owner is used.
    6869
    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`.
     70If 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`.
    7071
    71 == Hiding Fields and Adding Custom Fields
     72
     73== Hiding Fields and Adding Custom Fields ==
    7274
    7375Many 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''.
    … …  
    7577Trac also lets you add your own custom ticket fields. See TracTicketsCustomFields for more information.
    7678
    77 == Assign-to as Drop-Down List
    7879
    79 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 an authenticated session** and possess the `TICKET_MODIFY` [TracPermissions permissions].
     80== Assign-to as Drop-Down List ==
    8081
    81 An authenticated session will be created the first time a user authenticates with the project. You can manually add an authenticated session using the ["TracAdmin#?session add" trac-admin] `session add` command. The `:1` suffix on the session id (i.e. username) is the key to creating an authenticated session:
    82 {{{#!sh
    83 trac-admin /path/to/projenv session add <sid>:1 [name] [email]
    84 }}}
     82If 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].
    8583
    8684You may find the dropdown list is //overpopulated// with users that are no longer active in the project. Revoking authentication privileges will not remove the session data that is used to populate the dropdown list. The [wiki:TracAdmin trac-admin] command can be used to list and remove sessions:
    … …  
    9896
    9997'''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].
    101  
    102  - Activating this option may cause some performance degradation. Read more about this in the [trac:TracPerformance#Configuration Trac performance] page.
     98 - If you need serious flexibility and aren't afraid of a little plugin coding of your own, see [http://trac-hacks.org/wiki/FlexibleAssignToPlugin FlexibleAssignTo].
    10399
    104 == Preset Values for New Tickets
     100 -  Activating this option may cause some performance degradation. Read more about this in the [trac:TracPerformance#Configuration Trac performance] page.
     101
     102== Preset Values for New Tickets ==
    105103
    106104To 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:
    107105
    108  * '''type''' — The type droplist.
    109  * '''reporter''' — Name or email of the reporter.
    110  * '''summary''' — Summary line for the ticket.
    111  * '''description''' — Long description of the ticket.
    112  * '''component''' — The component dropdown list.
    113  * '''version''' — The version dropdown list.
    114  * '''severity''' — The severity dropdown list.
    115  * '''keywords''' — The keywords or tags.
    116  * '''priority''' — The priority dropdown list.
    117  * '''milestone''' — The milestone dropdown list.
    118  * '''owner''' — The person responsible for the ticket.
    119  * '''cc''' — The list of emails for notifying about the ticket change.
     106 * '''type''' — The type droplist
     107 * '''reporter''' — Name or email of the reporter
     108 * '''summary''' — Summary line for the ticket
     109 * '''description''' — Long description of the ticket
     110 * '''component''' — The component droplist
     111 * '''version''' — The version droplist
     112 * '''severity''' — The severity droplist
     113 * '''keywords''' — The keywords
     114 * '''priority''' — The priority droplist
     115 * '''milestone''' — The milestone droplist
     116 * '''owner''' — The person responsible for the ticket
     117 * '''cc''' — The list of emails for notifying about the ticket change
    120118
    121 Example: `[/newticket?summary=Compile%20Error&version=1.0&component=gui]`
     119Example: ''`[/newticket?summary=Compile%20Error&version=1.0&component=gui]`''
    122120
    123121----
    124 See also: TracGuide, TracWiki, TracTicketsCustomFields, TracNotification, TracReports, TracQuery
     122See also:  TracGuide, TracWiki, TracTicketsCustomFields, TracNotification, TracReports, TracQuery