Issues with Journal Plugin: Task Detection Fails in Daily Notes

[uttamjain8]

Please check that this issue hasn't been reported before.

• I searched previous Bug Reports didn't find any similar reports.

Expected Behavior

Tasks from daily notes created using the Journals plugin should be detected and displayed by the Day Planner plugin in the side panel and calendar view.

Current behaviour

Issue #1: Tasks Not Detected from Daily Notes with Journals Plugin

• I am using the Journals plugin to create daily notes with the following settings:
  • Path: MyFolder/YYYY/MMM/DD MMM YY (folders and subfolders are created).
  • File Name Format: DD MMM YY.
• When tasks are added under the defined heading in these daily notes, the Day Planner side panel view does not detect or display them.
• However, when I create a daily note directly using Day Planner (with file names in YYYY-MM-DD format), tasks in these notes appear correctly in the Calendar View.

---

Issue #2: Tasks Not Scanned with Additional Task Scanning Setting

• I tried configuring the Data View Input as MyFolder. to enable additional task scanning.
• My daily notes are structured with specific headings and levels as required for the Day Planner plugin.
• Despite this configuration, tasks from these notes still do not appear in the Calendar View.

Steps to reproduce

1. Create a daily note using the Journals plugin with the specified path and file name format.
2. Add tasks under the defined heading for the Day Planner plugin.
3. Observe that the tasks do not appear in the side panel or calendar view.
4. Configure the Data View Input for additional task scanning and observe no change.

Which Operating Systems are you using?

• Android
• iPhone/iPad
• Linux
• macOS
• Windows

Obsidian Version

1.7.6

Possible solution

• Enhance the Day Planner plugin settings to allow users to specify custom folder paths and file name formats for detecting daily notes.
• Provide a configuration field where users can define the path (e.g., MyFolder/YYYY/MMM/DD MMM YY) and file naming convention (e.g., DD MMM YY).
• Implement a parser to identify and map these custom formats to the Day Planner's expected structure.