Project

General

Profile

Actions

Bug #2048

closed

xmera Omnia - Bug #2054: Bug fixing in DMS, Project Types, and Issue Sync

Projects without custom fields enabled won't get importet

Added by liaham about 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Affected Version:
Compatible Redmine Version:

Description

The validation of project custom fields is based on all existing custom fields instead of those enabled for a given project type.

Projects with a project type having no project custom field enabled at all would not get imported.

Version 4.4.1 and 4.5.0 are affected.

Actions #1

Updated by liaham about 1 year ago

  • Description updated (diff)
Actions #2

Updated by liaham about 1 year ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

These scenarios w.r.t. custom fields are supported now:

  1. Project creation is based on a given project type

    1. Project type has assigned project custom fields (pcf)
      1. Import without pcf ==> valid
      2. Import with enabled pcf ==> valid
      3. Import with not enabled pcf ==> invalid
    2. Project type has no project custom fields assigned
      1. Import without pcf ==> valid
      2. Import with not enabled pcf ==> invalid
  2. Project creation without given project type

    1. Import without pcf ==> valid
    2. Import with existing pcf ==> valid
    3. Import with not existing pcf ==> invalid
Actions #3

Updated by liaham about 1 year ago

  • Parent task set to #2054
Actions

Also available in: Atom PDF