Enhancement: Option to hide completed tasks in the navigation sidebar
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
The issue names no files or tests. Start by locating the left navigation sidebar and the code that renders completed tasks, then review the Deck app's archived-card behavior as the stated precedent. Done means users can toggle completed-task visibility globally or per list without deleting the tasks or losing their history.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
When tasks are marked as completed, they remain permanently visible in the left navigation sidebar (under the respective calendar/list). Over time, this leads to a cluttered sidebar where completed tasks mix with open ones, making it harder to get a quick overview of what still needs to be done.
Describe the solution you'd like
An option to hide completed tasks from the left navigation sidebar — similar to how the Deck app handles archived cards. Ideally this would be a toggle (show/hide completed tasks) either per list or as a global setting, so users can choose whether completed tasks should be visible in the navigation or not.
Describe alternatives you've considered
- Moving completed tasks to a separate calendar manually — works but requires constant manual effort
- Deleting completed tasks — not desirable if a history is needed
- Custom CSS workaround — fragile and depends on internal HTML structure
Additional context
The Deck app already implements a similar concept for archived cards, so there is precedent within the Nextcloud ecosystem for this pattern.
Please use the 👍 reaction if you are affected by the same issue.
- Dominant language
- JavaScript
- Stars
- 710
- Forks
- 125
- Avg merge
- 19h 37m
- Merged PRs (30d)
- 12
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/tasks
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nextcloud/tasks#3240 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nextcloud/tasks#3111 · 1 comment ·
Maintainers usually reply within 1 day
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
nextcloud/tasks#122 · 9 comments · 25 reactions ·
Maintainers usually reply within 1 day
-
1. to develop
Difficulty 5/5 Over a week Newbie friendliness 39/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
remotion-dev/remotion#13341 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
svix/svix-webhooks#2808 ·
Maintainers usually reply within 1 day
-
enhancement should-have ux
Difficulty 2/5 1-3 hours Newbie friendliness 72/100