Redmine

Custom Values for Projects allows administrators to restrict the available values of issue list custom fields independently for each project.

The restrictions are consistently applied to issue forms, context menus, bulk editing and server-side validation. Both dropdown and checkbox display
styles are supported.

Project members with the appropriate permission can configure the allowed values from the project settings. Removing the project-specific configuration
restores all values defined globally by the Redmine administrator.

Main features:

• Per-project values for issue list custom fields
• Dropdown and checkbox support
• Server-side validation
• Context menu and bulk-edit support
• Project-level permission management
• Safe upgrade path from plugin 1.x
• English, Czech and Spanish translations
• Automated tests for Redmine 5.0, 5.1, 6.0 and 6.1

Compatible with Redmine 5.x and 6.x.

Requirements¶

• Redmine 5.0, 5.1, 6.0 or 6.1
• No additional gems are required

Installation¶

From the Redmine installation directory, clone the plugin into the plugins directory:

bc. cd /path/to/redmine/plugins
  git clone https://github.com/redmineservices/redmine_custom_values_projects.git
  cd redmine_custom_values_projects
  git checkout v2.0.0
  cd ../..

Run the plugin migrations:

bc. bundle exec rake redmine:plugins:migrate NAME=redmine_custom_values_projects RAILS_ENV=production

Restart Redmine.

Open a project and go to:

bc. Settings → Custom fields

Grant the Manage possible values permission to the project roles that should be allowed to configure the available values.

Upgrade from version 1.x¶

Back up the Redmine database before upgrading.

Update the plugin files:

bc. cd /path/to/redmine/plugins/redmine_custom_values_projects
  git fetch --tags
  git checkout v2.0.0
  cd ../..

Run the migrations:

bc. bundle exec rake redmine:plugins:migrate NAME=redmine_custom_values_projects RAILS_ENV=production

Restart Redmine.

Version 2.0 adds a uniqueness constraint. If duplicate configurations exist for the same project and custom field, the migration retains the oldest
  record.

Uninstallation¶

Back up the database and revert all plugin migrations:

bc. bundle exec rake redmine:plugins:migrate NAME=redmine_custom_values_projects VERSION=0 RAILS_ENV=production

Remove the plugin directory and restart Redmine:

bc. rm -rf plugins/redmine_custom_values_projects