fix(journal): planned subtasks are hidden from the planned list and header count

Open
  • Is something wrong?
#422 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
backend-api-design

Research direction

Start with the get_journal implementation and the code that builds the Planned tasks (N) header; inspect how planned dates and subtasks are represented, then look at related issue #349 for context. Trace the journal tests for planned tasks and subtasks, if present. Done means day planned subtasks are visibly distinguishable from unplanned open subtasks and are included in the header count.

Written by the indexing model from the issue text.

Description

Problem

A subtask planned for a day (e.g. #170 under #127) is only shown nested beneath its parent in the journal view (get_journal), and it is not counted in the Planned tasks (N) header. A task that is genuinely planned for the day is therefore easy to miss, and the header count understates the day's plan.

Example (journal 2026-11-05): the header reads Planned tasks (3), but #127 lists 19 open subtasks and only #170 is actually planned for that day. Nothing marks it apart from the other 18.

Expected

  • A subtask planned for the day appears in the planned list in its own right, or is clearly marked as planned within its parent's nested list.
  • The Planned tasks (N) header counts every task planned for that day, subtasks included.
  • Open subtasks that are not planned for that day stay distinguishable from those that are.

Related

  • #349 (show only a day's own subtasks under a parent)
  • #366 (tracking: journal subtask display)

Raised from TaskFlow task #183.

Dominant language
C#
Stars
1
Forks
0
Avg merge
2h 2m
Merged PRs (30d)
98

Getting set up

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.

More from nevridge/TaskFlow

All issues in nevridge/TaskFlow

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.