nextcloud / nextcloud/mail

Add a setting to control where snoozed emails reappear

Open
#13,382 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

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.

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

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.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.