Problem
Tags currently behave like groups — each connection can only have one tag. This makes them redundant with Groups and prevents flexible organization and filtering. There is no way to assign multiple tags or filter by combinations of tags.
Proposed solution
Allow assigning multiple tags per connection and implement proper tag-based filtering (including multi-select with AND/OR logic). Tags should work as independent labels, not mutually exclusive groups.
Alternatives considered
- Using Groups instead of Tags — not suitable, since Groups are limited to one per connection
- Creating more granular Groups — leads to clutter and does not scale
- Keeping current behavior — does not solve filtering and flexibility issues
Related database type
None
Problem
Tags currently behave like groups — each connection can only have one tag. This makes them redundant with Groups and prevents flexible organization and filtering. There is no way to assign multiple tags or filter by combinations of tags.
Proposed solution
Allow assigning multiple tags per connection and implement proper tag-based filtering (including multi-select with AND/OR logic). Tags should work as independent labels, not mutually exclusive groups.
Alternatives considered
Related database type
None