Allow changing Multiple Tags selection from OR to AND #4675

Open
opened 2026-02-28 04:11:23 -05:00 by deekerman · 4 comments
Owner

Originally created by @rfrancocantero on GitHub (Feb 6, 2026).

No related

🔖 Feature description

I posted this as a bug but perhaps it fits better here:

Hi,

I've created multiple tags for my monitors.
A few of them have one tag but a few have multiple tags.

Location 1 has Tag A, B and C
Location 2 has Tag B and C and D
Now if I filter in the menu on Tag B, it shows Location 1 and 2, that's correct.
But then I click on Tag D also in the filter menu. It displays two green check marks but the second filter is not applied. So I keep seeing Location 1 and 2 but I should only see Location 2.

Image

✔️ Solution

It should display combined results

Alternatives

Provide an option for the user in the settings menu so that the end user can choose how this works.

📝 Additional Context

No response

Originally created by @rfrancocantero on GitHub (Feb 6, 2026). ### 📑 I have found these related issues/pull requests No related ### 🔖 Feature description I posted this as a bug but perhaps it fits better here: Hi, I've created multiple tags for my monitors. A few of them have one tag but a few have multiple tags. Location 1 has Tag A, B and C Location 2 has Tag B and C and D Now if I filter in the menu on Tag B, it shows Location 1 and 2, that's correct. But then I click on Tag D also in the filter menu. It displays two green check marks but the second filter is not applied. So I keep seeing Location 1 and 2 but I should only see Location 2. <img width="131" height="253" alt="Image" src="https://github.com/user-attachments/assets/997334e5-7a50-4946-a16c-b37c7ad1cfe8" /> ### ✔️ Solution It should display combined results ### ❓ Alternatives Provide an option for the user in the settings menu so that the end user can choose how this works. ### 📝 Additional Context _No response_
Author
Owner

@CommanderStorm commented on GitHub (Feb 6, 2026):

I asked you in https://github.com/louislam/uptime-kuma/issues/6873#issuecomment-3859086306 to

Not sure what the actual expected UX-pattern is, but a feature request explaining the different options and why we should choose one of these options is likely best.

So what are the differnt options that you identified?

@CommanderStorm commented on GitHub (Feb 6, 2026): I asked you in https://github.com/louislam/uptime-kuma/issues/6873#issuecomment-3859086306 to > Not sure what the actual expected UX-pattern is, but a feature request explaining the different options and why we should choose one of these options is likely best. So what are the differnt options that you identified?
Author
Owner

@rfrancocantero commented on GitHub (Feb 6, 2026):

The different options I see for multi-tag filtering are:

OR / “Match any selected tag” (current behavior): show monitors that have at least one of the selected tags.
Example: selecting Tag B + Tag D shows monitors with B or D.

AND / “Match all selected tags” (cascading / “pipe down”): show only monitors that have all selected tags.
Example: selecting Tag B + Tag D shows only monitors that have B and D.

My expectation (and preference) was AND/Match all, because selecting additional tags usually feels like narrowing/refining the result set, not expanding it.

A good compromise could be to support both via a simple UI toggle or setting, e.g. Any (OR) ↔ All (AND), so users can choose the behavior that matches their workflow.

@rfrancocantero commented on GitHub (Feb 6, 2026): The different options I see for multi-tag filtering are: OR / “Match any selected tag” (current behavior): show monitors that have at least one of the selected tags. Example: selecting Tag B + Tag D shows monitors with B or D. AND / “Match all selected tags” (cascading / “pipe down”): show only monitors that have all selected tags. Example: selecting Tag B + Tag D shows only monitors that have B and D. My expectation (and preference) was AND/Match all, because selecting additional tags usually feels like narrowing/refining the result set, not expanding it. A good compromise could be to support both via a simple UI toggle or setting, e.g. Any (OR) ↔ All (AND), so users can choose the behavior that matches their workflow.
Author
Owner

@karthikeya-333 commented on GitHub (Feb 19, 2026):

Hi, is this issue still open? If yes, I would like to work on it @CommanderStorm

@karthikeya-333 commented on GitHub (Feb 19, 2026): Hi, is this issue still open? If yes, I would like to work on it @CommanderStorm
Author
Owner

@rfrancocantero commented on GitHub (Feb 19, 2026):

Yes please! I would love that!! Thank you sooo much!

@rfrancocantero commented on GitHub (Feb 19, 2026): Yes please! I would love that!! Thank you sooo much!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#4675
No description provided.