logseq / logseq/logseq

Scheduled Todo item missing context in journal

Open
#1,855 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

:type/bug query
Dominant language
Clojure
Stars
45k
Forks
2.8k
Avg merge
1d 22h
Merged PRs (30d)
105

Description

Describe the bug
Todo's that are listed within the "Scheduled and Deadline" section of the journal entry are missing context.

To Reproduce
Create a new task that is X levels deep in some page hierarchy and schedule it for today (see image below).

task-missing-context

Expected behavior
Within the "Scheduled and Deadline" section, the todo only lists the page from which the todo comes from - in this case "Test Page". But we've lost all context of where within Test Page this task exists (in this case Test Page > Level 1 > Level 2 > Level 3 > Level 4).

Without any context (e.g. page > project > sub project > sub-sub project > task) we could have multiple tasks from the same page but have little idea what the task really means. For instance, a simple task like "write report" is meaningless without its context: which project?, which sub project?, etc.

Desktop:

  • macOS Big Sur 11.3.1
  • Canary 0.0.2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the journal entry rendering for the "Scheduled and Deadline" section and reproduce the case with a task nested several levels under a page. Trace how the task's source context is displayed, then verify that the full hierarchy appears for nested tasks and that existing scheduled-task entries still render correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
clojure
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.