Expose all mail as a CalDAV list, with each message a task.
Nobody has claimed this yet.
- 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, I utilise labels to track completion of mail. However, I would prefer to be able to utilise NC's task management infrastructure in its stead, because every message I receive via e-mail is a task.
Describe the solution you'd like
Expose all mail as a CalDAV list, with each message a task. Completion states can be trivially exposed as labels to third-party mail clients.
Additional context
This does not duplicate to issues/6127. I consider what it proposes to be a workaround at best, especially because it means that:
-
as
issues/11255describes, two objects then exist -
the user must create a task for all mail, whereas, for me, every message is, always, a task
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. Start by reviewing the existing mail and task-management integration points, then define how all messages map to a CalDAV task list and how completion states map to labels; done means this works without manually creating duplicate tasks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100