-
Notifications
You must be signed in to change notification settings - Fork 18
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
(FR) Make the date adjust after completion #67
Comments
Hi @bepolymathe Yes, a completed task gets the ✅ emoji. The rules are for task status:
You'll notice in the above examples that the date is just a bare date. i.e.: It is not using Tasks format. In the example you provided, there is one status (Incomplete, in process, cancelled, done) derived from the However, if you use the Tasks plugin format, you can configure the "how to process multiple dates" setting to choose how you want your calendar events to be created. I'll explain them here: If you choose "prefer start date"
If you choose "create multiple events"
If you choose "prefer due date"
Hopefully the above is clear. I'm wondering if "create multiple events" suits your use case here. |
Thank you for these details. It’s clear. I'm just wondering if changing the status to "done" might be accompanied by an adjustment of the I use the "create multiple events" option and I'm very happy with it (thank you very much for implementing it 👍🏼). |
Hi @andrewbrereton
Unless I'm mistaken, when a task is completed, it's simply marked with an icon ✅. This is very practical, but it would be even more so if the date were changed to match the completion date. Very useful when you visualize everything in a calendar.
For example. An event planned for tomorrow but finally carried out today could appear as ✅ today. For this to happen, the scheduled date would have to be adjusted. Without affecting the due date.
Eventually, "Initial planning: 2024-02-20" could appear in the description for those who need to keep track.
Your opinion about this ?
The text was updated successfully, but these errors were encountered: