logseq / logseq/db-test

Today’s Journal default query does not include pages with status: Doing

Open
#1,124 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
No language data
Stars
28
Forks
2
PR merge metrics
No merged PRs in 30d

Description

### Search first

- [x] I searched and no similar issues were found

### What Happened?

In Today’s Journal, default query for nodes with the Doing value of the status property does not include pages. However, block nodes with the same status: Doing property are queried correctly.

### Reproduce the Bug

1. Create a page.
2. Set its status property to Doing.
3. Open Today’s Journal and check the default query for nodes with the status property set to Doing.

### Expected Behavior

The page should be included in the query results because its status property is set to Doing.

### Screenshots

_No response_

### Files

_No response_

### Browser, Desktop or Mobile Platform Information

logseq 2.0.1

### Additional Context

_No response_

### Are you willing to submit a PR? If you know how to fix the bug.

- [ ] I'm willing to submit a PR (Thank you!)

Contributor guide

No contributing guide indexed for this repository

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

No files or tests are named. Reproduce the issue in Today’s Journal by comparing a page and a block with status set to Doing, then trace the default query entry point; done means the page appears in the results alongside the block.

Written by the indexing model from the issue text.

Assessment

Domain
database
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.