Add a setting to control where snoozed emails reappear
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript
- Domain
- frontend
Research direction
No files or tests are named. Start by locating the snooze-return flow and the user-settings implementation, then trace how the message list orders returned emails. Done means adding the setting with the current behavior as default and supporting top-of-list placement without changing the original received date.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Currently, when a snoozed email becomes due, it is moved back to its original folder and sorted according to its original received date.
As a result, older emails may reappear far down in the message list instead of at the top. Even though the email is marked as unread, it can easily be overlooked, especially in mailboxes with a high volume of messages.
For many users, the purpose of snoozing an email is to bring it back to their attention at a specific time. The current chronological sorting can make it appear as if the snoozed email did not return at all.
Describe the solution you'd like
Add a user setting that allows users to choose where snoozed emails appear when they become due.
Suggested options:
Sort by original received date
Show at the top of the message list
The current behavior could remain the default to avoid changing existing workflows.
The original received date should remain unchanged in the email metadata. The setting should only affect how the message is positioned or displayed in the message list after it returns.
Describe alternatives you've considered
Possible workarounds include:
Filtering the mailbox for unread emails
Marking snoozed emails as favorites
Moving emails to a dedicated folder such as “Later” or “To do” before snoozing them
Manually searching for the email after the snooze time has passed
These alternatives require additional steps and do not provide the same clear visibility as showing the returned snoozed email at the top of the message list.
Additional context
This feature request was written and translated with the help of AI due to a language barrier.
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 363
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 86
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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 nextcloud/mail
-
1. to develop enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
nextcloud/mail#13841 · 3 comments ·
Maintainers usually reply within 1 day
-
1. to develop enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
nextcloud/mail#13828 · 1 comment ·
Maintainers usually reply within 1 day
-
Show email next to name in Search dropdownPossibly taken @vansh-nagar claimed this 18 days ago. Open1. to develop enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
nextcloud/mail#13703 · 1 comment ·
Maintainers usually reply within 1 day
-
ISO-2022-JP emails are garbled in Mail 5.10.12 [Minimal fix available]Possibly taken @neconohitomi claimed this 38 days ago. Open1. to develop bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
nextcloud/mail#13472 · 1 comment ·
Maintainers usually reply within 1 day
-
1. to develop technical debt
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
Similar issues
-
🐞 bug pending triage
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
CircuitVerse/CircuitVerse#8025 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
schmayterling/hibi#245 ·
Maintainers usually reply within 1 day
-
factory-active task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug package:vitest
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
cloudflare/workers-sdk#16255 · 1 comment ·
Maintainers usually reply within 1 day
-
Proxy and MCP URLs with an empty authority parse as a different hostPossibly taken @ericcaiwx-star claimed this today. Openclawsweeper:bulk-filed clawsweeper:linked-pr-open clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster P2
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
openclaw/openclaw-enterprise#2384 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day