Content
Updated by Andrej Sandorf 1 day 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."
### **Expected Behavior**
The export should let the user know this is due to the no longer available disabled custom field in filter query.
**Discussion**
The filter field is displayed with not actually shown or used in the UI as expected.
But it's still in the query which then breaks when a read warning string and the option work package export is attempted.
Unchecking 'Used as a filter' for the a custom field should warn a user to remove if there are queries using it as such. Or,  the filter should be removed from their filters
On saving/"saving as" queries
The "bad request" response of the query, the invalid filter field request is removed (instead of crashing angular)
<br> &quot;cf N doesn&#39;t exist&quot;.
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."
### **Expected Behavior**
The export should let the user know this is due to the no longer available
**Discussion**
But it&#39;s still in the query which then breaks when
Unchecking &#39;Used as a filter&#39;
On saving/"saving as"
The &quot;bad request&quot; response of
<br>