Fields, attachments and notes

The myTracker data are organized in issue records. An issue record have fixed properties and can have custom properties. One issue-record can have several attachments and notes.

Type of issue fields:
  1. Choice list - User can choose one of defined value (Combo Box filled with strings)
  2. Choice user - User can choose one user myTracker user (Combo Box with user names)
  3. String - String with maximal length 50 characters
  4. Float - Floating point number with range from 5.0 x 10^-324 to 1.7 x 10^308
  5. Integer - 32 bit signed integer
  6. Date - SQL Date type
  7. Date with time - SQL Timestamp
  8. Boolean - can have one of (True, False) value (Checkbox)
  9. Tree - User can choose one of defined value. The values are organized hierarchical in trees.

Beside type have issue fields these properties:
  1. Name - DB table column name/variable name
  2. Range from-to validity range for numbers
  3. Label - Form control caption
  4. Hint - Form control hint
  5. Input mask - string field input mask
  6. Read only - Cannot modify the property value
  7. Required at - Not required, required at opening, required at closing
  8. Length - Set the maximal length for string fields (the overall maximum length can you set in project properties)
  9. Regular expression - Multiline input fields input format can you declare with regular expression instead of input mask (for one line input fields).
Choice list
Is specialized issue field type used for quick choice of limited number of values. For example issue type with values : Bug, Change request, New feature, Knowledge. Each value can have own font style (Normal, Bold, Italic) and font color.

It is possible to define disabled user group for every Choice list element. It means, this user group can not select (and view) this element. Very useful for distinguishing user groups (programmer vs. beta tester).
Another feature visible on the picture is the possibility to define disabled elements for each element of choice list. This feature allowed to define element selection order (tree). For example: we have a property for bug status with elements : submited, analysing, programming, testing, solved and not a bug.

We can define a changes tree:

And now translate it to program logic program. For submited are disabled programming, testing, solved and not a bug. For all but bug are disabled submited, analysing, programming, testing and solved.

Every server must have these fixed properties:

Name Type
ID Integer
NAME String
DEADLINE Date with time
FROMTIME Date with time
SUBMITER Choice user


Trees are evolution of choice list. The tree unlike choice lists allow you effective manage dozens values. Very handy for organising program functions into modules and groups. So you can define a tree structure:

And so it will be live rendered.