Custom fields

Custom fields allow you to add additional information to several types of data used in Redmine. See 'custom field types' for all types of data which come with support for custom fields.
Each custom field can be defined to be of a certain type.

Custom field types

A custom field can be of one the following types:

  • Integer: positive or negative number
  • String: one single line of input
  • Text: multiple lines text (supports rich text formatting as of 2.50)
  • Long Text: resizeable multiple lines of text (supports rich text formatting as of 2.50)
  • Date: date
  • Boolean: checkbox
  • List: drop down list
  • User custom field format that can be used to reference a project member
  • Version custom field format that can be used to reference version
  • TODO, update list...
    Some validations can be defined for each custom field:
  • Min - max length: minimum and maximum length for the field (0 means that there is no restriction)
  • Regular Expression: a regular expression can be used to validate the field content. Examples:
    1. 4 capital letters followed by one or several digits
      ^\[A-Z]{4}\d+$
    2. characters only, no digits
      ^[^0-9]*$

A full list of regular expressions can be found in the Ruby Users Guide.

  • Possible values: possible values for the "List" fields. One line for each value.

Custom field supporting data types

Fields for Issues

Data in issue custom fields can be used and/or will be displayed in issues, issue lists, custom queries and the Timelog report.

  • Trackers: TODO
  • Required: field which is required in order to create/save an issue
  • 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 Project settings).
  • Used as a filter: TODO
  • Searchable: field which is searchable using the Redmine search function

Fields for Spent time entries

Data in spent time entry custom fields can be used and/or will be displayed in the Timelog report.

  • Required: field which is required in order to create/save a spent time entry

Fields for Projects

Data in project custom fields can be used and/or will be displayed in the Project overview.

  • Required: field which is required in order to create/save a project
  • Searchable: field which is searchable using the Redmine search function

Fields for Versions

Data in version custom fields can be used and/or will be displayed in the Roadmap and the Version overview.

  • Required: field which is required in order to create/save a version

Fields for Users

Data in user custom fields can be used and/or will be displayed in the user profiles.

  • Required: field which is required in order to create/save a user
  • Visible: field which is displayed in the user profile
  • Editable: field which is editable by the Redmine user owning the user account

Fields for Groups

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.

Fields for Activities (time tracking)

Data in time tracking activity custom fields can be used and/or will be displayed in the Timelog report and the Project settings. See also #4077 for some details about this nifty feature.

  • Required: field which is required in order to create/save an activity

Fields for Issue priorities

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.

Fields for Document categories

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.