RusRedmineCustomFields » History » Version 1
Denis Savitskiy, 2011-06-30 16:13
| 1 | 1 | Denis Savitskiy | h1. Пользовательские поля |
|---|---|---|---|
| 2 | |||
| 3 | {{>toc}} |
||
| 4 | |||
| 5 | Пользовательские поля дают возможность добавлять дополнительную информацию некоторым типам данных, используемых в Redmine. Прочтите '[[RedmineCustomFields#Custom-field-types|custom field types]]' чтобы узнать все типы данных, которые поддерживают пользовательские поля. |
||
| 6 | Каждое пользовательское поле может быть определено в один из типов: [[RedmineCustomFields#Custom-field-supporting-data-types|certain type]]. |
||
| 7 | |||
| 8 | h2. Типы пользовательских полей |
||
| 9 | |||
| 10 | Пользовательские поля могут быть следующих типов: |
||
| 11 | |||
| 12 | * *Целочисленное*: положительное или отрицательное число |
||
| 13 | * *Строка*: строка ввода |
||
| 14 | * *Текст*: многострочный текст |
||
| 15 | * *Дата*: дата |
||
| 16 | * *Логический тип*: чекбокс |
||
| 17 | * *Список*: выпадающий список |
||
| 18 | |||
| 19 | |||
| 20 | Для каждого поля можно задать несколько проверок: |
||
| 21 | |||
| 22 | * *Минимальная - максимальная длина*: минимальная и максимальная длина поля (0 означает, что ограничений нет) |
||
| 23 | * *Регулярное выражение*: можно использовать регулярное выражение для проверки содержимого поля. Примеры: |
||
| 24 | ## _за 4 заглавными буквами следует группа из нескольких цифр_ |
||
| 25 | <pre>^\[A-Z]{4}\d+$</pre> |
||
| 26 | ## _только символы, никаких цифр_ |
||
| 27 | <pre>^[^0-9]*$</pre> |
||
| 28 | |||
| 29 | * *Возможные значения*: возможные значения для поля "Список". В каждой строке одно значение. |
||
| 30 | |||
| 31 | h2. Custom field supporting data types |
||
| 32 | |||
| 33 | h3. Fields for Issues |
||
| 34 | |||
| 35 | 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 | |||
| 37 | * *Trackers*: TODO |
||
| 38 | * *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 | * *Used as a filter*: TODO |
||
| 41 | * *Searchable*: field which is searchable using the Redmine [[RedmineSearch|search function]] |
||
| 42 | |||
| 43 | h3. Fields for Spent time entries |
||
| 44 | |||
| 45 | Data in spent time entry custom fields can be used and/or will be displayed in the [[RedmineTimelogReport|Timelog report]]. |
||
| 46 | |||
| 47 | * *Required*: field which is required in order to create/save a spent time entry |
||
| 48 | |||
| 49 | h3. Fields for Projects |
||
| 50 | |||
| 51 | Data in project custom fields can be used and/or will be displayed in the [[RedmineProjectOverview|Project overview]]. |
||
| 52 | |||
| 53 | * *Required*: field which is required in order to create/save a project |
||
| 54 | * *Searchable*: field which is searchable using the Redmine [[RedmineSearch|search function]] |
||
| 55 | |||
| 56 | h3. Fields for Versions |
||
| 57 | |||
| 58 | Data in version custom fields can be used and/or will be displayed in the [[RedmineRoadmap|Roadmap]] and the [[RedmineVersion|Version overview]]. |
||
| 59 | |||
| 60 | * *Required*: field which is required in order to create/save a version |
||
| 61 | |||
| 62 | h3. Fields for Users |
||
| 63 | |||
| 64 | Data in user custom fields can be used and/or will be displayed in the [[RedmineUserProfiles|user profiles]]. |
||
| 65 | |||
| 66 | * *Required*: field which is required in order to create/save a user |
||
| 67 | * *Editable*: field which is editable by the [[RedmineAccounts|Redmine user]] owning the user account |
||
| 68 | |||
| 69 | h3. Fields for Groups |
||
| 70 | |||
| 71 | *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 | |||
| 73 | h3. Fields for Activities (time tracking) |
||
| 74 | |||
| 75 | 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 | |||
| 77 | * *Required*: field which is required in order to create/save an activity |
||
| 78 | |||
| 79 | h3. Fields for Issue priorities |
||
| 80 | |||
| 81 | *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 | |||
| 83 | h3. Fields for Document categories |
||
| 84 | |||
| 85 | *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. |