Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Error-bug] subtasks #289

Open
lxxinli opened this issue Nov 29, 2024 · 0 comments
Open

[Error-bug] subtasks #289

lxxinli opened this issue Nov 29, 2024 · 0 comments

Comments

@lxxinli
Copy link

lxxinli commented Nov 29, 2024

QQ图片20241129103819

Bug Description:

As shown in the image, when there are too many subtasks, the entire task box gets filled with subtasks, causing buttons like the delete button to become unusable (they are pushed to the very top of the page and become inaccessible). I suspect this issue might be due to the lack of a scrollbar for the subtask box. I recommend adding a scrollbar to the subtask box to prevent such problems in the future.


Feature Suggestion:

Your software is incredibly well-designed and stands out from many other scheduling tools on the market, which often end up overcrowding users' schedules. I have a suggestion for an important feature that could further improve the user experience:
Currently, subtasks are not fully utilized. For example, I can drag a large task into the weekly schedule, but I don’t know which specific subtasks need to be completed on that day to consider the larger task as done. Could you add the ability to drag and drop individual subtasks into specific days? This way, users can directly check off individual subtasks for a given day. Additionally, each subtask could display which larger task it belongs to for better tracking and mapping. Once all subtasks are completed, the corresponding large task could automatically be marked as done (since they are linked, the system would know which larger task to mark).


Advanced Feature Suggestion:

It would be great if tasks could also display a completion percentage. For instance, if a large task contains 10 subtasks and I complete 3 of them, the large task could show “30%” progress next to it, providing positive feedback and showing incremental progress.
Going further, since different subtasks may have varying workloads, you could allow users to set weight proportions for each subtask to make progress calculations more accurate.
For large tasks without subtasks, you could also let users manually set the percentage of completion. This way, users wouldn’t need to wait until a task is 100% complete to mark it as done, reducing the cognitive load of large leaps in progress.


Final Thanks:

Thank you so much for your thoughtful design! This software is truly amazing, and I look forward to seeing it become even more powerful!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant