Changes between Version 13 and Version 14 of TicketCreateButtonsPlugin
- Timestamp:
- May 5, 2018, 10:50:10 AM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TicketCreateButtonsPlugin
v13 v14 29 29 '''Notes''': 30 30 1. Below instructions could be specific to some operating systems. Please help expanding these instructions. 31 1. Generic installation guidelines are available at [http://trac.edgewall.org/wiki/TracPlugins TracPlugins]. 32 1. `[sudo]`, when used, is optional case you already have enough authority to modify your server. 31 1. Generic installation guidelines are available at [TracPlugins#InstallingaTracplugin TracPlugins]. 32 1. The use of `[sudo]` is optional when you already have authorisation to modify your server settings. 33 34 '''Installation steps''': 33 35 34 36 1. '''Install''' plugin: … … 58 60 parents.inherit = type, milestone, parents 59 61 }}} 60 * or accessing your Admin panel (under selected Trac environment {{{ ..admin/general/plugins }}}).62 * or accessing your Admin panel under selected Trac environment {{{ ..admin/general/plugins}}}. 61 63 [[BR]][[BR]] 62 64 1. '''Restart''' web server: … … 65 67 [sudo] /etc/init.d/apache2 restart 66 68 }}} 67 [[BR]] [[BR]]68 1. '''Test''' if this component is working properly (main environment and secondary ones if also exists).69 1. If the plugin is installed correct , the configuration you have made should reflect ontickets.69 [[BR]] 70 1. '''Test''' if this component is working properly, ie the main environment and any secondary ones. 71 1. If the plugin is installed correctly, the configuration you have made should reflect on these tickets. 70 72 71 73 == Configuration 72 74 73 1. Under the appropriate section inside a TracIni file you can customize ticket properties as below:74 75 76 77 78 where `<field-name>.<argument> = value` can be one or many frombelow:75 Under the appropriate section inside a TracIni file you can customize ticket properties as follows: 76 {{{#!ini 77 [ticket-create-buttons] 78 <field-name>.<argument> = value 79 }}} 80 where `<field-name>.<argument> = value` can be any from the below: 79 81 * R - Required 80 82 * O - Optional 83 81 84 ||'''Argument''' ||'''Version''' ||'''R / O''' ||'''Description''' ||'''Default''' || 82 85 || `tag` || >= 0.1 || R ||Argument to `genshi.filters.Transfomer` used to find the ticket form element to which the button will be prepended. Typically a custom field name.[[BR]]* Example: {{{ blockedby.tag = .//td[@headers="h_blockedby"] }}} || None || … … 87 90 || `set` || >= 0.1 || O ||Comma-separated list of `field:value` pairs for setting values in the new ticket. The `set` field override `inherit` and `link` fields. [[BR]]* Example: {{{ set = keywords:Foo }}} sets the new ticket's keywords field to Foo.|| None || 88 91 89 == Example92 === Sample configurations 90 93 91 94 1. '''Example''': Using this plugin with MasterTicketsPlugin, the following configuration creates buttons to create predecessor and successor tickets:
