Content
View differences
Updated by Andrej Sandorf 9 months ago
### **Environment**:
Your OpenProject Version: 12.0.1
### **Steps to reproduce:**
1. Create a work package custom field, tick 'Used as a filter'
2. Create a work package query using this custom field as a filter
3. Edit the custom field and uncheck 'Used as a filter'
4. Open the work package query and try to export as, say, XLS
### **Actual Behavior**
A red error message with "Bad request." "HTTP failure response ..."
### **Expected Behavior**
The export should either
A) Work but not consider the filter
B) Not work but let the user know this is due to the disabled custom field field, also the filter should be removed from the query
**Discussion**
The filter is not actually shown or used in the UI as expected.
But it's still in the query which then breaks when a work package export is attempted.
Unchecking 'Used as a filter' for a custom field should warn a user if there are queries using it as such. Or, the filter should be removed from queries
The "bad request" response of the request is "cf N doesn't exist".
Your OpenProject Version: 12.0.1
### **Steps to reproduce:**
1. Create a work package custom field, tick 'Used as a filter'
A red error message with "Bad request."
### **Expected Behavior**
The export should
A) Work but not consider the filter
B) Not work but
**Discussion**
The filter is not actually shown or used in the UI as expected.
But it's still in the query which then breaks when a work package export is attempted.
Unchecking 'Used as a filter' for a custom field should warn a user if there are queries using it as such. Or, the filter should be removed from queries
The "bad request" response of the request is "cf N doesn't exist".