| | 1 | = Ticket Component = |
| | 2 | |
| | 3 | This page is about the "component" attribute associated with Tickets - as distinct from 'components' which extend the trac software. |
| | 4 | |
| | 5 | The Component attribute allows tickets to be grouped according to the different parts of your project. |
| | 6 | |
| | 7 | Components can be configured through the python interface TracAdmin. If you remove all the components the option disappears from the ticket forms. |
| | 8 | |
| | 9 | The mandatory "owner" attribute specifies an individual to whom such tickets will be assigned by default. |
| | 10 | |
| | 11 | ---- |
| | 12 | {{{ |
| | 13 | > Hi Folks, |
| | 14 | > |
| | 15 | > Can anybody explain why a ticket component type has an owner. When you |
| | 16 | > add a new component in TracAdmin, the syntax is |
| | 17 | > |
| | 18 | > component add <name> <owner> |
| | 19 | > |
| | 20 | > but what is this <owner>, and where is it used? All my components have |
| | 21 | > the mysterious default 'somebody' as the owner for want of anything better. |
| | 22 | |
| | 23 | Because components are given default owner. In new project env all |
| | 24 | components has default owner of "somebody". |
| | 25 | |
| | 26 | You can though change owner at the time of entering new ticket or later |
| | 27 | with assign to - functionality in tickets. |
| | 28 | }}} |
