mirror of
https://github.com/Ylianst/MeshCentral.git
synced 2026-03-02 23:07:02 -05:00
Default Device Filter to an "and" search instead of an "or" search #1770
Labels
No labels
Can't Replicate
Closed
Feedback
Fixed - Please Verify & Close
Low Priority
Plugin's in use
Sponsor required
Stale
bootstrap
bug
docker
docs
duplicate
enhancement
help wanted
important
invalid
question
sponsor found
temporarily fixed
upstream fix needed
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/MeshCentral#1770
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @routerino on GitHub (Nov 11, 2020).
Something I've noticed is that if you are doing a search in the filter section at the top, it will search for all phrases that are separated by a space. For example, if you search for "windows linux", it will search for devices with "linux" in the parameter or "windows" in the parameter.
Usually if I'm resorting to the filter, I'm trying to find a specific computer or device. In that situation an "and" search would be more appropriate. For example I would search for
<location> kiosklooking for a kiosk at a specific location. Instead, I get every computer at that location as well as every kiosk in the database. It's not useful in that regard.Having the ability to toggle between an "and" search or an "or" search would be a very useful feature.
@sdlopexvidri commented on GitHub (Nov 13, 2020):
Hii, yes that could be a good option when you have a lot of devices and need to make a kind of double filter
@kpetrow commented on GitHub (Apr 22, 2025):
I am noticing this in --filter option in meshcntrl.js when filter string "catd9 "+serialNumber it returns all catd9. Not good
@github-actions[bot] commented on GitHub (Jun 21, 2025):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
@github-actions[bot] commented on GitHub (Jun 28, 2025):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please feel free to reopen it.