View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0025626 | mantisbt | filters | public | 2019-03-20 05:48 | 2019-04-09 11:34 |
Reporter | senex | Assigned To | cproensa | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | assigned | Resolution | open | ||
Product Version | 2.20.0 | ||||
Summary | 0025626: Saved filters (old and new ones) not working correctly | ||||
Description | We recently updated to 2.20.0 and everything seemed to work fine. Now, if you access the "View issues" page and try to use a saved filter (only tested with private ones), the page refreshes but no values have been selected. However, if you access the "Manage filter" page, edit one of the filters there and then update it, the filter starts working again. Has the filter format changed in any way in 2.20? | ||||
Additional Information | MySQL 8.0.12 | ||||
Tags | No tags attached. | ||||
Please clear your browser cache to reolad new javascript files and try again |
|
I already tried that, but it does not help unfortunately. Noticed another detail though:
And I assume that OpCache shouldn't be a problem? Or are you actually generating php files on the fly? |
|
Not the structure I can't reproduce any of your issues. Filters are selected. They can be saved and afterwards selected, working as expected. This tracker is currently updated to >2.20. Can you reproduce those issues here? |
|
No, but I also can't create new filters here. I think the problem lies within the saving of the filters. But as you can't reproduce the issue, I guess there is something wrong with our installation? I will look furhter into it. |
|
Yes, we have this issue also after just updating to 2.20.0 from 2.10.0. We have found that when the filters box is expanded, then selecting a filter in the Load drop-down has no effect. However, if we collapse the filter toolbox, then selecting a filter in the drop-down works correctly and the page updates to show the reports we were expecting. As suggested above, doing a cache clear of the View Issues page has fixed. |
|
@senex as explained it seems to be related to an outdated javascript cache in the browser after upgrading |
|
Yeah, even though I cleared the cache already, it now seems to work. Hmm, strange. |
|
I also ran into this problem. |
|
yes. that would be a solution. |
|