RedmineCustomFields » History » Version 4
Mischa The Evil, 2010-10-12 03:53
Lots of updates, fixes and additions (some TBD's left)
1 | 1 | Jean-Philippe Lang | h1. Custom fields |
---|---|---|---|
2 | |||
3 | 4 | Mischa The Evil | {{>toc}} |
4 | 1 | Jean-Philippe Lang | |
5 | 4 | Mischa The Evil | Custom fields allow you to add additional information to several types of data used in Redmine. See '[[RedmineCustomFields#Custom-field-types|custom field types]]' for all types of data which come with support for custom fields. |
6 | Each custom field can be defined to be of a [[RedmineCustomFields#Custom-field-supporting-data-types|certain type]]. |
||
7 | |||
8 | h2. Custom field types |
||
9 | |||
10 | A custom field can be of one the following types: |
||
11 | |||
12 | 1 | Jean-Philippe Lang | * *Integer*: positive or negative number |
13 | * *String*: one single line of input |
||
14 | * *Text*: multiple lines text |
||
15 | * *Date*: date |
||
16 | * *Boolean*: checkbox |
||
17 | * *List*: drop down list |
||
18 | |||
19 | Some validations can be defined for each custom field: |
||
20 | |||
21 | * *Min - max length* : minimum and maximum length for the field (0 means that there is no restriction) |
||
22 | * *Regular Expression* : a regular expression can be used to validate the field content |
||
23 | |||
24 | Examples: |
||
25 | |||
26 | ^\[A-Z]{4}\d+$ : 4 capital letters followed by one or several digits |
||
27 | 3 | Tharuka Pathirana | |
28 | 1 | Jean-Philippe Lang | ^[^0-9]*$ : characters only - no digits |
29 | |||
30 | * *Possible values*: possible values for the "List" fields. One line for each value. |
||
31 | |||
32 | 4 | Mischa The Evil | h2. Custom field supporting data types |
33 | 1 | Jean-Philippe Lang | |
34 | 4 | Mischa The Evil | h3. Fields for Issues |
35 | |||
36 | * *Trackers*: TBD |
||
37 | * *Required*: field which is required in order to create/save an issue |
||
38 | 1 | Jean-Philippe Lang | * *For all projects*: if checked, this field is used for the issues of all the projects. If unchecked, each project can choose whether or not to use the field for its issues (see [[RedmineProjectSettings|Project settings]]). |
39 | 4 | Mischa The Evil | * *Used as a filter*: TBD |
40 | * *Searchable*: TBD |
||
41 | 1 | Jean-Philippe Lang | |
42 | 4 | Mischa The Evil | h3. Fields for Spent time entries |
43 | 1 | Jean-Philippe Lang | |
44 | 4 | Mischa The Evil | * *Required*: field which is required in order to create/save a spent time entry |
45 | 1 | Jean-Philippe Lang | |
46 | 4 | Mischa The Evil | h3. Fields for Projects |
47 | 1 | Jean-Philippe Lang | |
48 | 4 | Mischa The Evil | * *Required*: field which is required in order to create/save a project |
49 | 1 | Jean-Philippe Lang | |
50 | 4 | Mischa The Evil | h3. Fields for Versions |
51 | 1 | Jean-Philippe Lang | |
52 | 4 | Mischa The Evil | * *Required*: field which is required in order to create/save a version |
53 | |||
54 | h3. Fields for Users |
||
55 | |||
56 | * *Required*: field which is required in order to create/save a user |
||
57 | * *Editable*: field which is editable by [[RedmineAccounts|Redmine users]] |
||
58 | |||
59 | h3. Fields for Groups |
||
60 | |||
61 | * *Required*: field which is required in order to create/save a group |
||
62 | |||
63 | h3. Fields for Activities (time tracking) |
||
64 | |||
65 | * *Required*: field which is required in order to create/save an activity |
||
66 | |||
67 | h3. Fields for Issue priorities |
||
68 | |||
69 | *Note*: issue priority custom fields are not (yet) used in the Redmine core, though other plugins or themes _can_ use them |
||
70 | |||
71 | * *Required*: field which is required in order to create/save an issue priority |
||
72 | |||
73 | h3. Fields for Document categories |
||
74 | |||
75 | *Note*: document category custom fields are not (yet) used in the Redmine core, though other plugins or themes _can_ use them |
||
76 | |||
77 | * *Required*: field which is required in order to create/save a document category |