Obsidian integration: Scheduled dates
under review
M
Máté
Scheduled dates are as important as Due dates and built in functionality like "Use filename as Scheduled date for undated tasks" encourage the use of them. For me at least it would make sense for an uncompleted task to appear twice on my calendar, one occasion with the scheduled date (and for me this would be the default time blocking behavior), and one for due date.
Danny Hatcher
under review
M
Máté
For the record this is what I sent to Morgen team about how I imagine dates and times should work across the two applications:
- scheduled and due dates of obsidian tasks should be fetched as properties to Morgen to be filtered/grouped upon
- scheduled and due dates both should be displayed on the calendar how you explained, maybe with different icons for easier understanding
- putting a task on the calendar should update/set the scheduled date of the task in Obsidian
- putting a task on the calendar past the due date should update the due date according to preferences
Unfortunately Tasks plugin doesn't handle time, only date, but Obsidian day planner plugin (https://github.com/ivan-lednev/obsidian-day-planner) uses a clever workaround, maybe that should be used here too to sync back scheduled time to Obsidian.
Kenrez
This might be a weird workflow on my end, but I wanted to be able to schedule tasks from my daily template notes. The day review task would be at a certain scheduled time and, as an example, workouts as well. Once they're in Morgen, I could always move them around as need be. For now, I'll do recurring events and only check the tasks done in my notes to avoid all the manual scheduling.
Luke Barnard
I think it would make sense to have two-way sync with this kind of workflow:
- tasks that have a scheduled date are shown in the task sidebar under a custom filtered view, e.g. "Obsidian tasks scheduled for today" (or maybe we could enable a "Scheduled today" section in the sidebar?)
- once scheduled, the original task scheduled date is also updated if necessary, but for multiple instances it'll need a confirmation dialog because technically there will be multiple scheduled dates
- due date still behaves as it does today
Danny Hatcher
Luke Barnard Agreed.
I feel the schedule date would work but would become very tricky for multiple sessions.
This is the issue with all integrations with Morgen - darn you added feature 😂
D
Daniel
Danny Hatcher Fact is, Obsidian (and litterally all community plugins) can only handle one date/time, so syncing this information with Morgen fully will never work. Either the Obsidian Integraion kills the feature for multiple sessions (which should be avoided if possible, as the feature is great), or we find a formula, to select which time/date to sync back to obsidian. Here is my attempt at such a formulation:
The first scheduled time/date across all not-complete work sessions of a given task syncs back to the obsidian task. If the final work session is completed, the scheduled date stays unchanged.
There is a quirky inconsistency that this brings up:
A task is already scheduled for 2 sessions in morgen (eg. Jan 1st and Jan 2nd) -> The task in Obsidian shows Jan 1st. If I change the date of the task in Obsidian to Jan 3rd then I broke the rule formulated above, as the scheduled date in obsidian no longer corresponds to the first non-complete session. The resolution here might be, that morgen updates the scheduled date/time in obsidian to reflect morgen (in this case, to Jan 2nd.
What are your thoughts? Are there other quirky scenarios that could cause problems?
Danny Hatcher
Daniel: I think it would be one potential solution.
Syncing the 'start date' as the first scheduled sessions is what I have thought about.
A
Aaron Wade
Brenna told me this in a support request: "Morgen has always treated scheduled dates as the time outlined in the calendar to work on the task." To me, this is exactly the field you want to integrate into your calendar, for time blocking purposes. I use relatively few Due dates, because that is reserved for an external authority. Time blocking and planning my day revolves around when I decide to work on a task, which is the Scheduled date field.
D
Daniel
I agree with the importance of "scheduled dates" in the Obsidian integration, but rather have a different need: If I schedule a task in Morgen, I want Obsidian to know about when I scheduled it. I.e. I want Morgen to update the scheduled date for the Obsidian task in Obsidian.