Changes between Version 13 and Version 14 of TicketCreateButtonsPlugin


Ignore:
Timestamp:
May 5, 2018, 10:50:10 AM (18 months ago)
Author:
figaro
Comment:

Further cosmetic changes

Legend:

Unmodified
Added
Removed
Modified
  • TicketCreateButtonsPlugin

    v13 v14  
    2929'''Notes''':
    3030     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''':
    3335
    3436 1. '''Install''' plugin:
     
    5860       parents.inherit = type, milestone, parents
    5961       }}}
    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}}}.
    6163     [[BR]][[BR]]
    6264 1. '''Restart''' web server:
     
    6567       [sudo] /etc/init.d/apache2 restart
    6668       }}}
    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 on tickets.
     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.
    7072
    7173== Configuration
    7274
    73   1. Under the appropriate section inside a TracIni file you can customize ticket properties as below:
    74      {{{#!ini
    75        [ticket-create-buttons]
    76        <field-name>.<argument> = value
    77      }}}
    78      where `<field-name>.<argument> = value` can be one or many from below:
     75Under 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}}}
     80where `<field-name>.<argument> = value` can be any from the below:
    7981       * R - Required
    8082       * O - Optional
     83
    8184||'''Argument''' ||'''Version''' ||'''R / O''' ||'''Description''' ||'''Default''' ||
    8285||  `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  ||
     
    8790||  `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  ||
    8891
    89 == Example
     92=== Sample configurations
    9093
    9194  1. '''Example''': Using this plugin with MasterTicketsPlugin, the following configuration creates buttons to create predecessor and successor tickets: