[Feature request] (Optionally) load completed tasks automatically
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 706
- Forks
- 117
- Avg merge
- 8h 50m
- Merged PRs (30d)
- 18
Description
Currently, you have to explicitly click a button in order to load completed tasks every time you open a task list. However, in some cases, I always want to have completed tasks shown without having to click a button.
For example, I have a list I use as a grocery list, to which I do not frequently add new items, but I frequently check and uncheck the same items.
I would appreciate it a lot if there was a configurable option (ideally per list) whether or not to load completed tasks by default.
Also, I think completed subtasks whose parent task is not completed yet should always be shown. In my opinion, it is confusing that it only shows the non-completed subtasks (hence giving you an incomplete picture). In other words, it would make more sense to show all subtasks (including completed ones) of non-completed tasks.
Moreover, when you click the "load all completed tasks" button, it gets replaced by a "delete all completed tasks" button in the exact same location. I think this is a bit risky since you could unintentionally click it out of habit when you don't realize completed tasks are already loaded.
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
No file, test, or entry point is named. Start by locating the task-list loading controls and list settings, then verify that completed tasks can be configured per list, completed subtasks remain visible under incomplete parents, and loading tasks does not expose a destructive action in the same position.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100