Content
View differences
Updated by Till Breuer about 12 years ago
**System**
* Core version: 3.0.0.pre48
**Actual behavior**
* When deactivating a filterable custom field and deactivating it for a certain work package type, those work packages with that type aren’t filtered out
**Expected behavior**
* Only work packages that are allowed to have the custom field should be retrieved by the query
**Preconditions**
* Logged in as a project member with permissions to view work packages
* There is a filterable custom field and it has been activated for the project
**Steps to reproduce**
\# Set a custom value of a filterable custom field to a work package, remember the work package type
\# As an admin go to Adminitration -\> Custom fields and deactivate the custom field for the work package type
\# Go to Work packages index
\# Add a filter on the custom field that matches the custom value of the work package
\# Apply query
Update will require modifying the SQL creation in the query model. Or cleaning up after the allowed work package types are updated
* Core version: 3.0.0.pre48
**Actual behavior**
* When deactivating a filterable custom field and deactivating it for a certain work package type, those work packages with that type aren’t filtered out
**Expected behavior**
* Only work packages that are allowed to have the custom field should be retrieved by the query
**Preconditions**
* Logged in as a project member with permissions to view work packages
* There is a filterable custom field and it has been activated for the project
**Steps to reproduce**
\# Set a custom value of a filterable custom field to a work package, remember the work package type
\# As an admin go to Adminitration -\> Custom fields and deactivate the custom field for the work package type
\# Go to Work packages index
\# Add a filter on the custom field that matches the custom value of the work package
\# Apply query
Update will require modifying the SQL creation in the query model. Or cleaning up after the allowed work package types are updated