Edgewall Software

Changes between Version 33 and Version 34 of TimeTracking


Ignore:
Timestamp:
Feb 12, 2006, 10:08:25 PM (18 years ago)
Author:
Felix Collins
Comment:

Added documentation on using the fields added by the patch.

Legend:

Unmodified
Added
Removed
Modified
  • TimeTracking

    v33 v34  
    2424 * Add a ticket query
    2525 * Use a Subversion commit hook to log spent time
    26 
    27 === Adding new custom field types ===
    28 
    29 It is useful to have fields that only accept numbers, fields that only accept an entry when the ticket is created and perhaps a field that accumulates the numbers you enter?  This can be achieved with a patch to the appropriate .cs files and the addition of a little javascript.
    3026
    3127===== Screenshots =====
     
    174170 * I couldn't see the second milestone bars so hacked the roadmap.cs to see them ... until I realized that using units (4h instead of just 4 ...) was the problem. All working now, very nice, many thanks.
    175171
     172
     173----
     174
     175== Adding new custom field types ==
     176
     177It is useful to have fields that only accept numbers, fields that only accept an entry when the ticket is created and perhaps a field that accumulates the numbers you enter?  This can be achieved with a patch to the appropriate .cs files and the addition of a little javascript.  The changes can be found in the [http://projects.edgewall.com/trac/attachment/wiki/TimeTracking/CustomFieldsRev2827.patch patch file] attached.
     178
     179'''Description of new types:'''
     180
     181''integer''
     182
     183Allows only integer values such as "12" and "-98329847" to be entered into the custom field.
     184
     185''cumulative_integer''
     186
     187Like integer but only allows the user to enter a value that is added to the current value. Useful for accumulating work done on a ticket or dollars spent.
     188
     189''set_once_integer''
     190
     191Like integer but only allows the user to set a value when the ticket is created.  From then on the value is fixed.
     192
     193Syntax of ini file:
     194
     195<name> = <type>
     196
     197Example:
     198
     199{{{ [ticket-custom]
     200mycustominteger = integer
     201mycustominteger_cumulative = cumulative_integer
     202mycustominteger_setonce = set_once_integer
     203}}}
     204
     205
    176206