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

Allow tagging of subtasks #2946

Closed
Tracked by #3111
pdlourenco opened this issue Dec 29, 2023 · 4 comments
Closed
Tracked by #3111

Allow tagging of subtasks #2946

pdlourenco opened this issue Dec 29, 2023 · 4 comments

Comments

@pdlourenco
Copy link

First of all, thank you very much for this excellent tool. I use Super Productivity everyday, mostly for time tracking, but I am starting to use it more for planning my days.
In the course of the 2 years I've been using it, there were some minor issues that have since been solved brilliantly (e.g., the feature to split idle time, etc) - goes to show how attuned the Johannes is to the needs of the users.

Problem Statement

For some of my projects, I use tasks as chunks of work that can take several days (or weeks) to complete, and which I then break down into more digestible subtasks spread throughout that time period. Since subtasks cannot be individually tagged (or Today-ed), I end up having these tasks in "Today" for ages, cluttering that view with several subtasks that I don't need to worry about in the present.

Another aspect is that a subtask could require very different categories of subtasks, for example:

  • The main task is "Derive requirements". It has several subtasks
    • Meet with users
    • Share notes with experts
    • Write set of reqs.
    • etc

Ideally, if I want to check meetings I have to do, I would look at the "meeting" tag, but I would have to tag the major task instead.

❔ Possible Solution

Allow tagging of subtasks, including the "Today" tag. When in "Today" view, see only the subtasks marked as "Today" for a given task, unless the whole task is moved to the day.

⤴️ Describe alternatives you've considered

I've considered simply breaking down the large several-day-long tasks into other tasks instead of subtasks. That way all the features available for tasks can be used. For the example above, I would get

  • Derive requirements: meet with users
  • Derive requirements: share notes with experts
  • etc

But, naturally, I lose the relationship between these tasks. This relates to another possible improvement: adding relationships between tasks as mentioned in #2173.

➕ Additional context

Copy link

Thank you very much for opening up this issue! I am currently a bit overwhelmed by the many requests that arrive each week, so please forgive me, if I fail to respond personally. I am still very likely to at least skim read your request and I'll probably try to fix all (real) bugs if possible and I will likely review every single PR being made (please, give me a heads up if you intent to do so) and I will try to work on popular requests (please upvote via thumbs up on the original issue) whenever possible, but trying to respond to every single issue over the last years has been kind of draining and I need to adjust my approach for this project to remain fun for me and to make any progress with actually coding new stuff. Thanks for your understanding!

@johannesjo
Copy link
Owner

Thanks for opening this up! I also would like to see this even though the change is far from trivial.

Copy link

This issue has not received any updates in 90 days. Please comment, if this still relevant!

@github-actions github-actions bot added the Stale label Jul 30, 2024
@johannesjo
Copy link
Owner

This is now possible! :)

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

No branches or pull requests

3 participants