Project

General

Profile

Actions
Copy link

Bug #2126

closed

xmera Omnia - Collection #2125: Bug Fixing: Project Types, Tables

Creating a project based on a project type resets the types modules and cf to default values

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

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

100%

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

Description

Steps to reproduce:

  • Create a project type having module tracker and calendar enabled.
  • Create two project custom fields
    • is_accountable (bool)
    • ocm (text)
  • Fill out the custom fields in the project type master with true and 'company'.
  • Import a project via csv:
Name;Description;Identifier;Public;Parent;Inherit members;Object class;ocm
0900;;zdv_0900;False;;True;ocm-company;company
  • Go back to the project type master and look at the modules enabled and the custom field values. Both are reset to default.
  • Go to the new objects and see that everything is as expected.
Actions
Copy link
 #1

Updated by liaham about 1 year ago

  • Target version changed from unreleased to 4.4.4
Actions
Copy link
 #2

Updated by liaham about 1 year ago

  • Status changed from New to In Progress

It turns out that custom_values are moved to the project instead of copied. Therefore, the project type has no values anymore.

Actions
Copy link
 #3

Updated by liaham about 1 year ago

The problem is solved by reassigning the custom_values to the project type since the deeper reason for that behavior could not be found.

Enabled modules instead was a regression of version 4.4.3 and could be solved.

Actions
Copy link
 #4

Updated by liaham about 1 year ago

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

Also available in: Atom PDF