super-productivity
super-productivity copied to clipboard
johannesjo
Repeating task improvements (reminders, monthly tasks and specific times) (Repeat tasks, repeat tasks)
I think the basic goal should be to achieve a functionality like google calendar or Thunderbird offer for reoccurring events.
It should be possible to:
- Select several week days similar to how it is now.
- To create monthly tasks.
- ~~To either have an "all-day task" (just shows up on the list) or to specify a specific time (shows up with a reminder).~~ done
Imho less important, but maybe also nice to have would be
- Biweekly or triweekly (is this a word?? :D) tasks
- Yearly tasks
- Re-creating sub tasks (as optional feature)
- Even more funky re-creation patterns
Still unclear to me is (lacking a good concept):
- How to deal with the task creation or in other words when exactly should a task show up in its list and how to deal with all it's future instances?
- Should task meta data such as the description be the same among all instances per default?
- In what way to create sub tasks. Probably a simple solution is best, that just uses the title (maybe with the short syntax included) but ignores everything else. I'd like to keep things as simple as possible for this.
EDIT: It would be cool if you add a thumps add to the original issue, so I can get a rough picture on how strong the demand is for this.
Hi I was just about to create a feature request about repeating task when I found this. I'm personally using the repeating tasks for my daily routine tasks (I have for example a task for repeated stuff I do in the morning, and for monitoring the average time I spent on answering on our company's chat). So on my side the main problem I'm encountering is that except the "morning routine" I never really close those tasks since I'm using them through the all day, and I often forgot to close them at the end of the day, so it happens a lot that I got twice the same task appearing the following day.
I assume it's related to what you mention:
How to deal with the task creation or in other words when exactly should a task show up in its list and how to deal with all it's future instances?
So I guess we can imagine different possibilities:
- tasks might be auto-closeable at the end of the repetition period
- maybe some tasks are in fact never closed so it's always the same instance appearing (could be useful in my case since the "Answer on chat" task is not something I expect to really close one day)
Hope it's the right place to share those thoughts, let me know if you prefer that I create a feature request for this - maybe - quite specific need :)
I currently use a GNOME plugin called time++ that has several features similar to Super Productivity. Regarding repeating tasks, they support a specific syntax like "3d" (repeat every 3 days) and "x-3d" (repeat 3 days after completing), among other things.
See the last section in this table, it might give you some ideas: https://github.com/zagortenay333/timepp__gnome#todotxt-extensions.
As a first step it is now possible to specify a start time for repeating tasks.
Is it possible to have a more granular repeating option i.e. every few hours. My use case being medication reminders
@daya this won't work well with how repeating tasks are designed, but for stuff like this there is this issue #446
Another thing I would like to address (probably not entirely related to this thread) is how the existing instance of a repeating task is handled when a new instance is created. Right now, the older instance (i.e. task) is marked as "completed" even if the user didn't actually complete it.
For example: I have a repeating tasks about reading some book. I don't always read that book, and some sometimes I might finish the day without completing that task. The next day, when I open SupProd, and the new task are being created, the task from the previous day still shows up, but will be marked as completed. A new task will be created instead.
I would suggest to mark the old task as something other than "completed". Maybe "archived" instead? same goes to how it's saved in the backups (I can see it has "isDone": true and "doneOn" timestamp) and internally.
Why am I suggesting this? because I have some custom jupyter notebooks to analyze my work behavior, and marking these repeating tasks as completed even thought they are not is messing up my analysis.
The next day, when I open SupProd, and the new task are being created, the task from the previous day still shows up, but will be marked as completed. A new task will be created instead.
The idea behind this is, that much of the literature on productivity suggests to mark your tasks as done at the end of the day (but transfer it to the next days list if it isn't of course).
Not sure how your analyse looks like, but maybe you can delete the task instead and/or use tags??
@johannesjo Thank you for the clarification. Here are a couple more follow up questions, just to make sure I fully understand this 100%:
- Are these completed tasks included in the exports? and in the metrics and worklog?
- If yes, why? I didn't complete these tasks, or even do any work towards them, so it doesn't really make sense to include them.
I really appreciate your time :)
- Are these completed tasks included in the exports? and in the metrics and worklog?
Done tasks are, deleted tasks are not.
- If yes, why? I didn't complete these tasks, or even do any work towards them, so it doesn't really make sense to include them.
Because of what I mentioned above and in order to keep things simpler.
I would consider this a separate issue from what is mentioned in the description. Could you open up a new issue please?
How do I add the repeating tasks? I dont see an advanced menu anywhere
@Jayy001 & @tuaone please go to the discussions page for questions like this (you might also already find an answer there).
Most of the stuff has been implemented and should be available for testing on the edge channel shortly. Please let me know what you think!
This issue has not received any updates in 90 days. Please comment, if this still relevant!
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue has not received any updates in 90 days. Please comment, if this still relevant!
This issue has not received any updates in 90 days. Please comment, if this still relevant!
Not stale
On Sun, 28 May 2023 at 07:31, github-actions[bot] @.***> wrote:
This issue has not received any updates in 90 days. Please comment, if this still relevant!
— Reply to this email directly, view it on GitHub https://github.com/johannesjo/super-productivity/issues/948#issuecomment-1565797309, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACLRHEKHKPXXDBQ3ZH32WF3XIKWYDANCNFSM4YWU2YZA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
This issue has not received any updates in 90 days. Please comment, if this still relevant!
still relevant
On Thu, Oct 12, 2023 at 07:16 github-actions[bot] @.***> wrote:
This issue has not received any updates in 90 days. Please comment, if this still relevant!
— Reply to this email directly, view it on GitHub https://github.com/johannesjo/super-productivity/issues/948#issuecomment-1758785914, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACLRHEL6ZFBOY5UFE6YJNQDX65DYHANCNFSM4YWU2YZA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Something that I would really like to see in regards to the scheduling of recurring tasks, but which I suspect might be a little more involved, is something like "first/second/... <weekday> of the month", so for example "last Wednesday of the month". We have quite a number of meetings in our Community which are scheduled this way and it saddens me that I can't use recurring tasks for them. .__.
I am closing this in favor of separate new issues like: #2471 #2752 #2938
If you find anything is missing, please create a new issue and reference this one.