Content
View differences
Updated by Hagen Schink over 12 years ago
If I deactivate a custom field in a project and I edit a work package of a type that is assigned to that deactivated custom field, the next save of the work package contains a change for the deactivated custom field.
### Precondition
1. Type with custom field(s) exists (called **Type C** in the following)
2. Project with activated custom field(s) (regarding the custom field assigned to the Type) exists (called **Project C**)
### Reproduce
1. In **Project C** create a work package (called **WP C** in the following) of type **Type C** (set the custom fields activated by type **Type C**)
2. In project settings deactivate custom fields assigned to type **Type C**
3. Edit work package **WP C**
4. Change nothing and save the work package **WP C**
### Behavior
**Expected:** Deactivated custom fields appear to be deleted
**Actual:** No journal entry is created
### Precondition
1. Type with custom field(s) exists (called **Type C** in the following)
2. Project with activated custom field(s) (regarding the custom field assigned to the Type) exists (called **Project C**)
### Reproduce
1. In **Project C** create a work package (called **WP C** in the following) of type **Type C** (set the custom fields activated by type **Type C**)
2. In project settings deactivate custom fields assigned to type **Type C**
3. Edit work package **WP C**
4. Change nothing and save the work package **WP C**
### Behavior
**Expected:** Deactivated custom fields appear to be deleted
**Actual:** No journal entry is created