Project

General

Profile

Actions

Bug #163

closed

Treatment of project custom fields

Added by liaham about 4 years ago. Updated about 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Target version:
Start date:
02/18/2021
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Affected Version:
Compatible Redmine Version:

Description

Implementation

In admin area

Project types

If a project custom field should be disabled, a check will run in oder to find out if there are projects using the respective custom field (ProjectType#integrity_of_project_custom_fields). If so, a validation error is thrown to the user.

Project custom fields

In case an administrator tries to disable a certain project type for a project custom field, the same validation as above will run by delegation.

In project settings

When a authorized user tries to change the project type of a project an AciveRecord::Callback.before_validations will run.

This callback runs Project#revise_project_type_dependencies. The method again has two implementations:

  • prevent_custom_fields_from_deletion
  • delete_custom_fields_after_project_type_reassignment

Subtasks 2 (0 open2 closed)

Improvement #164: Revise the treatment of object custom fieldsClosedliaham02/18/2021

Actions
Improvement #165: Inform the user about project custom field value deletion when changing project typeRejectedliaham02/18/2021

Actions
Actions #1

Updated by liaham about 4 years ago

  • Description updated (diff)
Actions #2

Updated by liaham about 4 years ago

  • Description updated (diff)
Actions #3

Updated by liaham about 4 years ago

  • Target version changed from 4.1.0 to unplanned
Actions #4

Updated by liaham about 4 years ago

  • Status changed from New to Resolved
  • Target version changed from unplanned to 4.0.0

Project custom fields are treated as follows:

  • Project with project type: gets the fields of it's project type and can be configured individually by disabling or enabling fields in admin area
  • Project Type: is configurable in admin area
  • Project without project type: default Redmine behavior
Actions #5

Updated by liaham about 4 years ago

  • Status changed from Resolved to Rejected

Is not a problem anymore?

Actions

Also available in: Atom PDF