See #949
- Filters should be server side, because we limit the number of items we fetch from the server
- Filters will include (timestamp after/before, resource, action, authors)
- They will have different default values depending on the history page. For example, buckets won't have
record among selected resources by default.
- The adjusted filters will be persisted in local storage (per resource, ie. if user removes
create from buckets history, it won't be removed from collections history)
The challenge is about filtering authors, if we want to exclude the different kinds of authors:
plugin:remote-settingsaccount:adminldap:mleplatre@mozilla.com
Server side filters currently don't offer the ability to express: like_user_id=(ldap:* | account:*).
Instead of offering a checkbox for each authentication scheme, we could decide to leave it as we implemented it in Kinto/kinto-admin#3596, with just the ability to:
- show/hide plugin entries (
not_user_id=plugin:remote-settings)
- show/hide non human entries (
like_user_id=ldap:*)
┆Issue is synchronized with this Jira Task
See #949
recordamong selected resources by default.createfrom buckets history, it won't be removed from collections history)The challenge is about filtering authors, if we want to exclude the different kinds of authors:
plugin:remote-settingsaccount:adminldap:mleplatre@mozilla.comServer side filters currently don't offer the ability to express:
like_user_id=(ldap:* | account:*).Instead of offering a checkbox for each authentication scheme, we could decide to leave it as we implemented it in Kinto/kinto-admin#3596, with just the ability to:
not_user_id=plugin:remote-settings)like_user_id=ldap:*)┆Issue is synchronized with this Jira Task