A saved filter stores a JQL definition, not a frozen list of current results. It can support a board, dashboard gadget or recurring review. Give it a name that describes the population, then verify the query independently of that name.
A reusable definition should continue to select the right work after new records arrive. A list of today's issue keys may reproduce the current rows while missing tomorrow's valid work. The local checker changes data and adds boundary probes to test the definition's behavior. Sharing and ownership are separate fields. This lesson keeps filters private while you build their populations, then the next lesson opens the intended audience. Saving a filter does not grant users permission to browse every matching issue in a hosted site.
Save definitions that remain correct as work changes.