RedmineCustomFields » History » Version 7
Mischa The Evil, 2010-10-12 05:32
Some more doc
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 | 7 | Mischa The Evil | Data in issue custom fields can be used and/or displayed in [[RedmineIssues|issues]], [[RedmineIssueList|issue lists]], [[RedmineIssueList#Custom-queries|custom queries]] and the [[RedmineTimelogReport|Timelog report]]. |
37 | 5 | Mischa The Evil | |
38 | 4 | Mischa The Evil | * *Trackers*: TBD |
39 | * *Required*: field which is required in order to create/save an issue |
||
40 | * *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]]). |
||
41 | 1 | Jean-Philippe Lang | * *Used as a filter*: TBD |
42 | 5 | Mischa The Evil | * *Searchable*: field which is searchable using the Redmine [[RedmineSearch|search function]] |
43 | 1 | Jean-Philippe Lang | |
44 | 4 | Mischa The Evil | h3. Fields for Spent time entries |
45 | 1 | Jean-Philippe Lang | |
46 | 5 | Mischa The Evil | Data in spent time entry custom fields can be used and/or displayed in the [[RedmineTimelogReport|Timelog report]]. |
47 | |||
48 | 4 | Mischa The Evil | * *Required*: field which is required in order to create/save a spent time entry |
49 | 1 | Jean-Philippe Lang | |
50 | 4 | Mischa The Evil | h3. Fields for Projects |
51 | 1 | Jean-Philippe Lang | |
52 | 5 | Mischa The Evil | Data in project custom fields can be used and/or displayed in the [[RedmineProjectOverview|Project overview]]. |
53 | |||
54 | 1 | Jean-Philippe Lang | * *Required*: field which is required in order to create/save a project |
55 | 5 | Mischa The Evil | * *Searchable*: field which is searchable using the Redmine [[RedmineSearch|search function]] |
56 | 1 | Jean-Philippe Lang | |
57 | 4 | Mischa The Evil | h3. Fields for Versions |
58 | 1 | Jean-Philippe Lang | |
59 | 6 | Mischa The Evil | Data in version custom fields can be used and/or displayed in the [[RedmineRoadmap|Roadmap]] and the [[RedmineVersion|Version overview]]. |
60 | |||
61 | 4 | Mischa The Evil | * *Required*: field which is required in order to create/save a version |
62 | |||
63 | h3. Fields for Users |
||
64 | |||
65 | 6 | Mischa The Evil | Data in user custom fields can be used and/or displayed in the [[RedmineUserProfiles|user profiles]]. |
66 | |||
67 | 1 | Jean-Philippe Lang | * *Required*: field which is required in order to create/save a user |
68 | 6 | Mischa The Evil | * *Editable*: field which is editable by the [[RedmineAccounts|Redmine user]] owning the user account |
69 | 4 | Mischa The Evil | |
70 | h3. Fields for Groups |
||
71 | 1 | Jean-Philippe Lang | |
72 | 7 | Mischa The Evil | *Note*: group custom fields are not (yet) used in the Redmine core, though other plugins or themes _can/may_ use them. |
73 | 6 | Mischa The Evil | |
74 | 4 | Mischa The Evil | * *Required*: field which is required in order to create/save a group |
75 | |||
76 | 1 | Jean-Philippe Lang | h3. Fields for Activities (time tracking) |
77 | |||
78 | 7 | Mischa The Evil | Data in time tracking activity custom fields can be used and/or displayed in the [[RedmineTimelogReport|Timelog report]] and the [[RedmineProjectSettings#Activities-time-tracking|Project settings]]. See also #4077 for some details about this nifty feature. |
79 | |||
80 | 4 | Mischa The Evil | * *Required*: field which is required in order to create/save an activity |
81 | 1 | Jean-Philippe Lang | |
82 | h3. Fields for Issue priorities |
||
83 | 4 | Mischa The Evil | |
84 | 7 | Mischa The Evil | *Note*: issue priority custom fields are not (yet) used in the Redmine core, though other plugins or themes _can/may_ use them. |
85 | 4 | Mischa The Evil | |
86 | 1 | Jean-Philippe Lang | * *Required*: field which is required in order to create/save an issue priority |
87 | |||
88 | 4 | Mischa The Evil | h3. Fields for Document categories |
89 | |||
90 | 7 | Mischa The Evil | *Note*: document category custom fields are not (yet) used in the Redmine core, though other plugins or themes _can/may_ use them. |
91 | 4 | Mischa The Evil | |
92 | * *Required*: field which is required in order to create/save a document category |