RedmineCustomFields » History » Version 13
  Jim Kovacs, 2011-06-14 04:01 
  
| 1 | 13 | Jim Kovacs | h1. Custom fields | 
|---|---|---|---|
| 2 | 1 | Jean-Philippe Lang | |
| 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 | 11 | Mischa The Evil | * TODO, update list... | 
| 19 | 1 | Jean-Philippe Lang | |
| 20 | Some validations can be defined for each custom field: | ||
| 21 | |||
| 22 | 11 | Mischa The Evil | * *Min - max length*: minimum and maximum length for the field (0 means that there is no restriction) | 
| 23 | * *Regular Expression*: a regular expression can be used to validate the field content. Examples: | ||
| 24 | ## _4 capital letters followed by one or several digits_ | ||
| 25 | <pre>^\[A-Z]{4}\d+$</pre> | ||
| 26 | ## _characters only, no digits_ | ||
| 27 | <pre>^[^0-9]*$</pre> | ||
| 28 | 1 | Jean-Philippe Lang | |
| 29 | * *Possible values*: possible values for the "List" fields. One line for each value. | ||
| 30 | |||
| 31 | h2. Custom field supporting data types | ||
| 32 | |||
| 33 | 4 | Mischa The Evil | h3. Fields for Issues | 
| 34 | |||
| 35 | 10 | Mischa The Evil | Data in issue custom fields can be used and/or will be displayed in [[RedmineIssues|issues]], [[RedmineIssueList|issue lists]], [[RedmineIssueList#Custom-queries|custom queries]] and the [[RedmineTimelogReport|Timelog report]]. | 
| 36 | 5 | Mischa The Evil | |
| 37 | 11 | Mischa The Evil | * *Trackers*: TODO | 
| 38 | 4 | Mischa The Evil | * *Required*: field which is required in order to create/save an issue | 
| 39 | * *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]]). | ||
| 40 | 11 | Mischa The Evil | * *Used as a filter*: TODO | 
| 41 | 5 | Mischa The Evil | * *Searchable*: field which is searchable using the Redmine [[RedmineSearch|search function]] | 
| 42 | 1 | Jean-Philippe Lang | |
| 43 | 4 | Mischa The Evil | h3. Fields for Spent time entries | 
| 44 | 1 | Jean-Philippe Lang | |
| 45 | 10 | Mischa The Evil | Data in spent time entry custom fields can be used and/or will be displayed in the [[RedmineTimelogReport|Timelog report]]. | 
| 46 | 5 | Mischa The Evil | |
| 47 | 4 | Mischa The Evil | * *Required*: field which is required in order to create/save a spent time entry | 
| 48 | 1 | Jean-Philippe Lang | |
| 49 | 4 | Mischa The Evil | h3. Fields for Projects | 
| 50 | 1 | Jean-Philippe Lang | |
| 51 | 10 | Mischa The Evil | Data in project custom fields can be used and/or will be displayed in the [[RedmineProjectOverview|Project overview]]. | 
| 52 | 5 | Mischa The Evil | |
| 53 | 1 | Jean-Philippe Lang | * *Required*: field which is required in order to create/save a project | 
| 54 | 5 | Mischa The Evil | * *Searchable*: field which is searchable using the Redmine [[RedmineSearch|search function]] | 
| 55 | 1 | Jean-Philippe Lang | |
| 56 | 4 | Mischa The Evil | h3. Fields for Versions | 
| 57 | 1 | Jean-Philippe Lang | |
| 58 | 10 | Mischa The Evil | Data in version custom fields can be used and/or will be displayed in the [[RedmineRoadmap|Roadmap]] and the [[RedmineVersion|Version overview]]. | 
| 59 | 6 | Mischa The Evil | |
| 60 | 4 | Mischa The Evil | * *Required*: field which is required in order to create/save a version | 
| 61 | |||
| 62 | h3. Fields for Users | ||
| 63 | |||
| 64 | 10 | Mischa The Evil | Data in user custom fields can be used and/or will be displayed in the [[RedmineUserProfiles|user profiles]]. | 
| 65 | 6 | Mischa The Evil | |
| 66 | 1 | Jean-Philippe Lang | * *Required*: field which is required in order to create/save a user | 
| 67 | 6 | Mischa The Evil | * *Editable*: field which is editable by the [[RedmineAccounts|Redmine user]] owning the user account | 
| 68 | 4 | Mischa The Evil | |
| 69 | h3. Fields for Groups | ||
| 70 | 1 | Jean-Philippe Lang | |
| 71 | 9 | Mischa The Evil | *Note*: group custom fields are not (yet) used in the Redmine core, though other plugins or themes _can/may_ use them. No setting here has any effect on any other parts of Redmine for the time being. | 
| 72 | 4 | Mischa The Evil | |
| 73 | 1 | Jean-Philippe Lang | h3. Fields for Activities (time tracking) | 
| 74 | |||
| 75 | 10 | Mischa The Evil | Data in time tracking activity custom fields can be used and/or will be displayed in the [[RedmineTimelogReport|Timelog report]] and the [[RedmineProjectSettings#Activities-time-tracking|Project settings]]. See also #4077 for some details about this nifty feature. | 
| 76 | 7 | Mischa The Evil | |
| 77 | 4 | Mischa The Evil | * *Required*: field which is required in order to create/save an activity | 
| 78 | 1 | Jean-Philippe Lang | |
| 79 | h3. Fields for Issue priorities | ||
| 80 | 4 | Mischa The Evil | |
| 81 | 9 | 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. No setting here has any effect on any other parts of Redmine for the time being. | 
| 82 | 8 | Felix Schäfer | |
| 83 | 7 | Mischa The Evil | h3. Fields for Document categories | 
| 84 | 4 | Mischa The Evil | |
| 85 | 9 | 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. No setting here has any effect on any other parts of Redmine for the time being. |