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
Also broken in this scenario:
* The filter button shows e.g. (2) filters in the count badge, but only one is shown in the filter configuration list, so users cannot remove it
* "Save" and "Save as" don't work, errors are thrown in the console, but no error message appears on screen
### **Actual Behavior**
A red error message with "Bad request."
### **Expected Behavior**
The export should work. let the user know this is due to the no longer available field in filter query.
The invalid filter field is omitted (not shown in displayed with a red warning string and the count badge or option for the filter list). user to remove it from their filters
Saving or saving as does work without throwing an exception in On saving/"saving as" the console query, the invalid filter field is removed (instead of crashing angular)
<br>
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
Also broken in this scenario:
* The filter button shows e.g. (2) filters in the count badge, but only one is shown in the filter configuration list, so users cannot remove it
* "Save" and "Save as" don't work, errors are thrown in the console, but no error message appears on screen
### **Actual Behavior**
A red error message with "Bad request."
### **Expected Behavior**
The export should work.
The invalid filter field is omitted (not shown in
Saving or saving as does work without throwing an exception in
<br>