You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's a small bug with the filter which hasn’t really affected me much, but I guess it's not the way it was intended to be. In the “save query” pop-up window you have the option to save filters alongside queries. If you go to your project and use that saved query, this works perfectly fine. However, this is not always the case when you’ve already used a number of queries (with different filtering options) in one session: if one of the filters is on (say author id 110) and you switch to a saved query with e.g. author id 111, it does not always change the filter to the one that was saved for that particular query. It seems to be the case that there is no problem with the filters if you switch between saved queries with different filters, but only if you switch from a regular, unsaved query with a particular filter to a saved query with another filter.
The text was updated successfully, but these errors were encountered:
There's a small bug with the filter which hasn’t really affected me much, but I guess it's not the way it was intended to be. In the “save query” pop-up window you have the option to save filters alongside queries. If you go to your project and use that saved query, this works perfectly fine. However, this is not always the case when you’ve already used a number of queries (with different filtering options) in one session: if one of the filters is on (say author id 110) and you switch to a saved query with e.g. author id 111, it does not always change the filter to the one that was saved for that particular query. It seems to be the case that there is no problem with the filters if you switch between saved queries with different filters, but only if you switch from a regular, unsaved query with a particular filter to a saved query with another filter.
The text was updated successfully, but these errors were encountered: