Project

General

Profile

Actions
Copy link

Bug #162

closed

All project custom fields will be validated even if they don't belong to the project under review

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

Status:
Closed
Priority:
Normal
Assignee:
liaham
Target version:
3.0.2
Start date:
02/17/2021
Due date:
% Done:

100%

Estimated time:
Affected Version:
Compatible Redmine Version:
Pull Request Link:

Description

Observation in xmera Omnia standard - Demo

Project custom fields are assigned to project types and project types are assigned to projects. When a project has a a project custom field through a project type what is required and is not filled, another project with another project type won't be saved when the required field is empty.

Actions
Copy link
 #1

Updated by liaham about 4 years ago

  • Project changed from Redmine Project Types Relations to Redmine Project Types
  • Status changed from New to In Progress
Actions
Copy link
 #2

Updated by liaham about 4 years ago

It is possible to recreate the desribed situation in a demo and development instance.

Debugging reveals that each project, independent of its project type, has a relation to all existing project custom fields:

@project.custom_field_values
Actions
Copy link
 #3

Updated by liaham about 4 years ago

  • Assignee set to liaham
  • Target version set to 4.1.0
Actions
Copy link
 #4

Updated by liaham about 4 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 0 to 100

This dependency is eleminated with resetting the custom_field_values before validation. For more information see Project#reset_project_custom_values! in the respective patch file.

Actions
Copy link
 #5

Updated by liaham about 4 years ago

  • Target version changed from 4.1.0 to 3.0.2
Actions
Copy link

Also available in: Atom PDF