Add support for recurring cards and tasks
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
Hi!
It would be helpful to support recurring cards or recurring tasks in Nextcloud Deck:
Users should be able to configure a card so that it is recreated or rescheduled automatically according to a defined recurrence rule.
For example:
- Every month on the 15th
- Every Monday
- Every two weeks
- On the first working day of each month
- Annually on a specific date
Expected behavior: When creating or editing a card, users should be able to define:
- A recurrence frequency
- A recurrence interval
- A due date or time
- An optional end date
- Whether the existing card should be reused or a new card should be created for each occurrence
For example, a card configured as “Due on the 15th of every month” could automatically create the next occurrence once the current card is completed, or create all upcoming occurrences according to the selected recurrence rule.
Possible options: A recurring card could be generated:
- When the previous occurrence is marked as completed
- A defined number of days before the next due date
- Automatically for a configurable number of future occurrences
It would also be useful to preserve selected card properties, such as:
- Stack
- Assigned users
- Labels
- Description
- Checklist
- Attachments
- Estimated effort
Use cases
- Monthly administrative tasks
- Regular maintenance and system checks
- Weekly team routines
- Recurring reporting deadlines
- Periodic reminders and organizational tasks
Is support for recurring cards or recurring due dates already planned or being considered?
Thank you!
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
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 card creation, editing, due-date, and completion flows in Nextcloud Deck, then clarify the recurrence model and generation rules with maintainers. Done would require an agreed, tested implementation covering the requested recurrence options and preserved card properties.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100