Right now, our filter components are not easier to maintain because of the base abstraction that is hard to extend, change, or test. To make that better I think we can:

• Split the current filter component into minor components so each resource can have its filter component
• Create tests for each of these new components
• Create e2e tests for the filters

After that we can safely improve the data load from:

• Template filter
  • Only fetch templates if there is a selected template.
  • When "All templates" is selected, it only should fetch data on click.
• User filter
  • Only fetch users if there is a selected user.
  • When "All users" is selected, it only should fetch data on click.
  • When the selected user is the logged-in user, use the current user profile data instead of fetching data.