Maybe, I am missing something, but shouldn’t the set filter not be over-written until browser session expiry/logout/application window close, as the behavior was before?
That would be the expected application behavior, as it is also in many other application paradigms. Right?
You mentioned about this reasoning below, but unfortunately the very same thing still holds true, but in a different context i.e. users will come to an active list they are still using and find that it no longer looks like it used 48 hours ago.
So maybe what you are trying to solve needs to be solved in some other way, as the current solution creates a similar problem the other way around?
If it is a new browser session, then filters could be reset (though that could also be argued, as you might want to support view restoration on session activation), but that would clearly not be acceptable on an existing active session.
I can imagine other scenarios as well where this would be an issue, example showing the list on a LED screen for a team with certain filters active, so they always see the view relevant for them. Having any kinds of filter time-outs will defeat those scenarios.
Sorry to pester you on this, but this one really annoys me as I can no longer trust the checkvist view on my browser and have to always double-check if the filters have changed since I last set them the way they should be.
---------- Update from 2020-04-17
Was working on a new checkvist page with no filters, but every few minutes it would automatically put the “priority:1” filter on it, requiring me to manually clear the filter out.
This happened 2-3 times in a span of 10 minutes. Likely this is not a new bug and related to the above topic itself, hence not reporting it as a new bug.