Skip to content

Filter Functions #673

Description

@Allyn56

Current State

This may duplicate some issues already open but wanted to talk about how the filter option could be improved using certain built in options. Right now, through Waypoint we have the ability to delete, move or copy caches from one database to another using, selected caches, flagged caches and all in filter. When selecting all in filter it seems OSAK assumes that if no filter is active, "all in filter" is all in database. This seems confusing from my workflow point of view. If the filter box shows none, then no filter is set. If I select the delete, move or copy "all in filter" option I am assuming I have a filter set. Nothing should be done if no filter is set using that option.

Proposed Improvement

If no filter is set the option "all in filter" should be grayed out or a popup screen should say "No filter set" and not perform anything for all of the caches in the database.

Expected Benefits

This would avoid performing something to all caches in your database thinking you have a filter set.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions