Edgewall Software

Changes between Version 2 and Version 3 of TicketComponent


Ignore:
Timestamp:
Oct 1, 2006, 10:55:19 PM (13 years ago)
Author:
sid@…
Comment:

Add more detail to the page and give an example

Legend:

Unmodified
Added
Removed
Modified
  • TicketComponent

    v2 v3  
    11= Ticket Component =
    22
    3 This page is about the "component" attribute associated with Tickets - as distinct from 'components' which extend the trac software.
     3The ''component'' ticket field allows tickets to be grouped according to the different parts of your project. This field can be set in all TracTickets, and then can be used to search, group, or filter tickets based on the relevant portion of the system.
    44
    5 The Component attribute allows tickets to be grouped according to the different parts of your project.
     5For example, the Trac project has defined some of its components as:
     6 * browser
     7 * changeset view
     8 * roadmap
     9 * tickets
     10If a bug is found in the roadmap code, the component would be set to ''roadmap''.
    611
    7 Components can be configured through the python interface TracAdmin.  If you remove all the components the option disappears from the ticket forms.
     12The components drop-down list can be configured through [wiki:TracAdmin trac-admin] or the WebAdmin plugin module. The mandatory ''owner'' attribute specifies the Trac user who tickets should be assigned to by default. A default component can be chosen as well for new tickets.
    813
    9 The mandatory "owner" attribute specifies an individual to whom such tickets will be assigned by default.
     14If all items are removed from the component list, then the component field will be completely hidden in the user interface.