| 23 | * Trac administrator should define the template for all ticket types: |
| 24 | * Login as administrator, open Admin -> Ticket System -> Ticket Template. |
| 25 | * '''Load''' the template of each ticket type, modify them and '''apply changes'''. |
| 26 | * After defined ticket template, normal user can create ticket using predefined template by '''change ticket types''' dropdown list items. |
| 27 | |
| 28 | '''The New Ticket page''' |
| 29 | |
| 30 | [[Image(NewTicketPage-v0.7.png, border=2)]] |
| 31 | |
| 32 | '''The Admin panel''' |
| 33 | |
| 34 | [[Image(AdminTicketTemplatePage-v0.7.png, border=2)]] |
| 35 | |
| 36 | About template parameters: |
| 37 | * This plugin supports template parameters which can be specified by URL. For example: |
| 38 | * The template: |
| 39 | {{{ |
| 40 | foo bar %(my_param)s baz qux |
| 41 | }}} |
| 42 | * Call newticket: |
| 43 | {{{ |
| 44 | http://yourtrac/newticket?my_param=anything&owner=myname |
| 45 | }}} |
| 46 | * Rendered: |
| 47 | {{{ |
| 48 | foo bar anything baz qux |
| 49 | }}} |
| 50 | * And the owner field would be populated with myname by Trac's default convention. |
| 51 | * '''Note''': be careful choosing the template parameter name to avoid conflicts with existing ticket field names. |
| 52 | |
119 | | == Example |
120 | | |
121 | | * Trac administrator should define the template for all ticket types: |
122 | | * Login as administrator, open Admin -> Ticket System -> Ticket Template. |
123 | | * '''Load''' the template of each ticket type, modify them and '''apply changes'''. |
124 | | * After defined ticket template, normal user can create ticket using predefined template by '''change ticket types''' dropdown list items. |
125 | | |
126 | | || Screen capture of the //New Ticket// page =|| [[Image(NewTicketPage-v0.7.png, 70%)]] || |
127 | | || Screen capture of the //Admin// panel =|| [[Image(AdminTicketTemplatePage-v0.7.png, 70%)]] || |
128 | | |
129 | | * About template parameters: |
130 | | * This plugin supports template parameters which can be specified by URL. For example: |
131 | | * The template: |
132 | | {{{ |
133 | | foo bar %(my_param)s baz qux |
134 | | }}} |
135 | | * Call newticket: |
136 | | {{{ |
137 | | http://yourtrac/newticket?my_param=anything&owner=myname |
138 | | }}} |
139 | | * Rendered: |
140 | | {{{ |
141 | | foo bar anything baz qux |
142 | | }}} |
143 | | * And the owner field would be populated with myname by Trac's default convention. |
144 | | * Note: be careful choosing the template parameter name to avoid conflicting with ticket field names. |
145 | | |