Top Menu

Jump to content
    Global modules

    Global modules

    • Home
    • Projects
    • Activity
    • Work packages
    • Gantt charts
    • Calendars
    • Team planners
    • Boards
    • News
    Home
    Home
Help
    Getting started
    • Introduction video
  • Help and support
    • Upgrade to Enterprise edition
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Enterprise support
  • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation

User menu

Sign in
Forgot your password?

or sign in with your existing account

OpenProject ID Google

Side Menu

Collapse project menu

  • Overview
  • Activity
    Activity
  • Roadmap
  • Work packages
    Work packages
  • Gantt charts
    Gantt charts
  • Calendars
    Calendars
  • Team planners
    Team planners
  • Boards
    Boards
  • News
  • Forums

Content

Expand project menu

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>
&amp;quot;cf N doesn&amp;#39;t exist&amp;quot;.

Back

Loading...