Add ability to search calendar events by subject/title
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
Research direction
Start by locating the CalendarEvent model and CalendarService, the entry points named in the issue, and inspect how existing event lookups are implemented. Done means exposing a backward-compatible subject/title search with case-insensitive partial matching, while confirming the performance and indexing approach.
Written by the indexing model from the issue text.
Description
Problem
Currently, calendar events are primarily accessed using internal identifiers (eventId) or date-based queries. However, there is no direct way to search events by their subject/title.
From a user perspective, event IDs are not meaningful, and users typically remember events by their names (e.g., meeting titles, subjects) rather than internal database identifiers.
This creates a usability limitation when users want to quickly locate a specific event.
Proposed Improvement
Introduce support for searching calendar events by subject/title.
At the service level, this could be implemented by:
Adding a model-layer query method (e.g., subject-based lookup)
Exposing a CalendarService method for text-based search
Supporting case-insensitive partial matches
Example use cases:
Searching for meetings by name
Quickly filtering large event lists
Enabling future UI search functionality
Why this is valuable
Improves overall calendar usability
Aligns with expected calendar/search behaviour
Removes reliance on internal event IDs
Reusable across UI, REST APIs, and integrations
Backward compatible enhancement
Possible Implementation Direction
A potential approach:
Add a subject-based query method in the CalendarEvent model
Use regex / indexed search with case-insensitive matching
Expose a search method via CalendarService
Performance considerations such as indexing on the subject field may also be relevant.
Additional Context
I’d be happy to work on the implementation if this enhancement is considered useful.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from RocketChat/Rocket.Chat
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
RocketChat/Rocket.Chat#42256 ·
-
type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
RocketChat/Rocket.Chat#42248 ·
-
todo type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
RocketChat/Rocket.Chat#42241 ·
-
todo type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
RocketChat/Rocket.Chat#42237 ·
-
type: feature
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
RocketChat/Rocket.Chat#42228 · 1 comment ·
All issues in RocketChat/Rocket.Chat
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·