Have something to say?

Tell us how we could make the product more useful to you.

In Review

Morgen ignores the Obsidian Tasks plugin's NON_TASK status type when importing checklist items

I use the Obsidian Tasks plugin with custom statuses. Several of them are explicitly configured as type "NON_TASK" in the plugin's data.json for example: { "symbol": "i", "name": "information", "type": "NON_TASK" } { "symbol": "k", "name": "key", "type": "NON_TASK" } These are meant to be informational sub-notes under a real task (e.g. a log line noting something I learned while doing the task), not tasks themselves. In Obsidian, the Tasks plugin correctly treats them as non-actionable. Morgen, however, reads any markdown checkbox line ("- [i] some text", "- [k] some text") straight from the file and imports it as a real task β€” grouped in the sidebar under labels that match the status names ("information", "key"). This happens even though the line has no due date, no πŸ†”, and is a sub-item indented under another task. Screenshot attached showing "information" and "key" groups full of what are just log notes, not tasks. Request: please read the Tasks plugin's customStatuses config (data.json) and skip any status whose "type" is "NON_TASK" when importing/scheduling from a vault. This would let Morgen coexist with the Tasks plugin's full status vocabulary instead of only the default checkbox states. As example, that’s a photo of a task that i forwarded to tomorrow , i used the symbol β€œi” to information , to information to me why i forwarded that task… Both fowarded symbol and information is recognized as non tasks by obsidian, but morgen catch that. Thanks!

Alan Victor 17 days ago

In Review

Drag down tasks from a timeline

It’s a big feature to implement, but it would be so handy to see all tasks (especially long term tasks with dependencies) in a timeline above the daily schedule so you could drag daily segments of each task down. Play around with the Claude artifact Potential benefits include: Quickly visualizing how much time each task should have allocated each day Easily drag and adjust start/end dates, time allocated for each tasks, dependencies, etc. Timeline bars get taller or shorter depending on how much time should be spent on them each day to get it done within set constraints You can get a sense of how busy each day could be without necessarily scheduling everything in advance to the minute (by looking at how many tasks are schedule-able from the timeline for a given day)

Caleb Koster 25 days ago

Bug: Availability slots default to the wrong duration, even though a duration is already set in the event.

When making an open invite, I'm clicking on the calendar to choose the different availability slots. Even though the default duration for the event is already set and predefined to 30 minutes, as I click on a new slot, it's choosing 15-minute time options instead of 30 minutes. I would expect that as I click for a different availability slot, it would default to the duration that is already set on this open invite that I'm creating. I don't want to have to go back and re-adjust the duration of each availability slot when it was already pre-configured in the duration. That doesn't make any sense to need to do all that extra effort. Also because it displays this way, I have no confidence in whether the tool is going to work correctly or not. Will this create a 30 min or 15 min event once everything is done?

Willard Moore about 1 month ago

1