nextcloud / nextcloud/mail

✉️ Mail brainstorming sessions

Open
#10,940 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
JavaScript
Stars
1k
Forks
348
Avg merge
12h 28m
Merged PRs (30d)
91

Description

Contributor week 2025

  • 5️⃣ https://github.com/nextcloud/mail/issues/5308
  • 5️⃣ https://github.com/nextcloud/mail/issues/11973
  • 4️⃣ Search is not very useful. Buggy, long loading times, no message text included in the search
  • 3️⃣ https://github.com/nextcloud/mail/issues/11767
  • 3️⃣ Overlaying composer, non blocking. Currently the mail composer in its small mode blocks the entire user interface. It would be nice to align with the industry and have an overlaying composer, bottom right, that does not block the rest of the UI.
  • 3️⃣ https://github.com/nextcloud/mail/issues/6589
  • 3️⃣ persist, and style more prominently, the “sending mail” popover in the top-right until the mail is sent. closing the browser tab (at some undefined point) before success leads to the mail 1. not being sent and 2. not being saved to drafts, so the UX should make it really clear that the tab needs to live (and remain online) until the mail is sent
  • 3️⃣ Mail filter templates, offer default filters provided by the admin (ex: work reports)
  • 2️⃣ Do not always reveal recipient details automatically when filling in a recipient. Or at least remember the last time a user dismissed it. This increases space for the actual content and reduces unnecessary clutter.
  • 2️⃣ Have a desktop app :)
  • 2️⃣ https://github.com/nextcloud/mail/issues/10671
  • 2️⃣ Quick emoji (❤️ 👍 ✅ 🍕 🐱 🐶 ) reply - reducing long thread/noise
  • 2️⃣ Subject line visibility - long subject line with ‘EXTERNAL’ takes too much space, and the actual subject cannot be seen. Any way to make it visible when it’s ‘External’ mail, or a short and colorful tagging system, maybe?
  • 2️⃣ Customize hover actions
  • 1️⃣ Spam filter
  • 1️⃣ reply to self in thread should not start a mail to yourself (but instead address the mail to non-self thread participants)
  • 1️⃣ allow using the Mail composer outside of a modal dialogue right now clicking outside of the modal by accident closes it and a notification that reads “Draft saved” appears. The WIP message is not actually stored in the “Drafts” folder however, but in the bottom right and gets lost when reloading the page
  • 1️⃣ closing a completely empty new mail (albeit with your signature prefilled) saves a draft. this leads to a huge pile of empty drafts, which is unhelpful (and hides actually valuable saved drafts in the pile)
  • 1️⃣ https://github.com/nextcloud/mail/issues/11788

Company week 2025

  • #10941
  • Have a non view blocking composer #2831
  • Improve Important flagging
  • Improve searching functionalities ( quick actions, simpler interface) related #9769
  • Don’t scroll in long email body container , expand the message instead
  • Shortcuts ( change mailboxes, archive, spam) #10936
  • Search in body in quick actions
  • group tagged messages in tagged folders ( potentially colour coded folders)
  • Rethink external mail flagging ( red mail address looks like an error )
  • add a quick mark as spam button (move to spam folder to help with server side spam detection)
  • mark quoted text with a different colour
  • Inaccurate send later due to cron job scheduling ( find a way to either warn the user or make it more accurate)
  • Slow initial sync for large mailboxes
  • Quick actions ( mark as read, archive )
  • Bug in mark all as ready ( mark all as read -> filter unread )

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

This issue is a brainstorming list rather than a scoped implementation task, and it names no files or tests. Start by selecting one unchecked proposal and opening its linked issue where available; define a single scope and acceptance criteria before locating the relevant code. It is done when that proposal has an agreed implementation and verification plan.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.