RocketChat / RocketChat/Rocket.Chat
Feature Request: Shared Channel Notes for Meetings
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Summary
I would like to propose a lightweight Shared Notes feature within channels to help teams document meeting discussions and decisions directly inside Rocket.Chat.
Problem
During meetings (especially video calls or active channel discussions), important decisions and action items are often:
-
Lost in long message histories
-
Scattered across threads
-
Stored in external tools
-
Difficult to revisit later
This creates friction when teams want to quickly review what was decided or assigned.
Proposed Solution
Introduce a persistent Shared Notes section per channel. For example:
A dedicated “Notes” tab inside each channel
Collaborative editing by channel members
Automatically saved and accessible anytime
Optionally, a prompt after a video call ends (e.g., “Create meeting notes?”)
This would help teams keep discussions, decisions, and documentation centralized within Rocket.Chat.
Possible Implementation Approach
This could potentially be implemented as:
A lightweight core feature
or
A Rocket.Chat App, if better suited as an extension rather than core functionality
Additional Context
The goal is not to replace full document tools, but to provide a simple, integrated way to maintain structured meeting notes within the communication workflow.
I would love to hear feedback on whether this aligns with the current product direction, or if similar functionality already exists or has been explored.
Thank you for your time and consideration.
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.
Research direction
The issue names no files, tests, or entry points. First review existing channel features and determine whether shared notes belong in core or a Rocket.Chat App, then define the product scope and acceptance criteria for persistent notes, member editing, saving, access, and any post-call prompt.
Written by the indexing model from the issue text.
Assessment
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100