Content
View differences
Updated by Robin Wagner over 10 years ago
**Preconditions**
- Work package module activated.
- Custom field of type Boolean exists and can be set on existing work package.
**Steps to reproduce**
1. Open work package which has custom field set to “no”.
2. Edit the work package and set the value of the Boolean custom field to “yes”.
3. Filter for all work packages which have the custom field set to “yes”.
**Actual behavior**
- Work package which has just been edited is not included in filtered list.
- In fact, only work packages which have the Boolean custom field set to “yes” / true at creation are included in the filtered list (if one of those work packages is edited an the value is changed to “no” and back to “yes”, it’s no longer included in the filter either.)
**Expected behavior**
- Filtered list includes all work packages which match the filter criteria (i.e. the work package with custom field set to “yes”).
**Example**
- Example on community.openproject.org: https://community.openproject.org/projects/finnlabs/work\_packages?query\_id=815
- This filter should include the following work packages which are not shown in the filter: \#20456, \#20459, \#20449, \#20398, \#20419, \#20459
- Example on org-dev.qa.finn.de: https://org-dev.qa.finn.de/projects/14/work\_packages?query\_id=2572
- Should show the following work packages which are not shown: 23344, 23289, 22150, 22167, 23349
**Screenshot**
- There are work packages with a Boolean CF in a project:
- When filtering for them, they are not shown:
**QA system**
- org-dev.qa.finn.de
- OpenProject 5.0.0
- Work package module activated.
- Custom field of type Boolean exists and can be set on existing work package.
**Steps to reproduce**
1. Open work package which has custom field set to “no”.
2. Edit the work package and set the value of the Boolean custom field to “yes”.
3. Filter for all work packages which have the custom field set to “yes”.
**Actual behavior**
- Work package which has just been edited is not included in filtered list.
- In fact, only work packages which have the Boolean custom field set to “yes” / true at creation are included in the filtered list (if one of those work packages is edited an the value is changed to “no” and back to “yes”, it’s no longer included in the filter either.)
**Expected behavior**
- Filtered list includes all work packages which match the filter criteria (i.e. the work package with custom field set to “yes”).
**Example**
- Example on community.openproject.org: https://community.openproject.org/projects/finnlabs/work\_packages?query\_id=815
- This filter should include the following work packages which are not shown in the filter: \#20456, \#20459, \#20449, \#20398, \#20419, \#20459
- Example on org-dev.qa.finn.de: https://org-dev.qa.finn.de/projects/14/work\_packages?query\_id=2572
- Should show the following work packages which are not shown: 23344, 23289, 22150, 22167, 23349
**Screenshot**
- There are work packages with a Boolean CF in a project:
- When filtering for them, they are not shown:
**QA system**
- org-dev.qa.finn.de
- OpenProject 5.0.0