logseq / logseq/logseq

Priority tags not sorting

Open
#12,483 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

### Search first

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

### What Happened?

Hoping this isn't a duplicate, I'm not Git-savvy enough to properly search issues.

At some point, adding /a /b /c to items no longer sorts them by priority like it used to. The ones I've seen this on are /later tasks, but I've tried switching to /now and just making them normal bullet pointed items, no change.

Image

### Reproduce the Bug

1. Create a list of 3 items, tasks, etc
2. Type /a on the final one
3. Type /b on the middle one
4. Type /c on the first one
5. Items do not reorder
6. Refresh page by going to whiteboards or something, then back to journal
7. No change
8. Close app, reopen, sync
9. No change

### Expected Behavior

In the past, I've been able to use /a /b /c to help order tasks within the NOW or LATER classification. Assigning /a to a task would put it above all others, leaving it without a classification would put it below C.

### Screenshots

Image

### Desktop or Mobile Platform Information

App Version: 0.10.15
Git Revision: 03bcefb
Platform: Mozilla/5.0 (Macintosh Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML like Gecko) Logseq/0.10.15 Chrome/140.0.7339.240 Electron/38.4.0 Safari/537.36
Language: en-US
Plugins:

### 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

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 reproducing the ordering issue in the journal with NOW or LATER items, using the /a, /b, and /c steps described. Trace the priority-sorting entry point for journal items and verify the behavior after refresh and restart. Done means items order from /a to /c, with unclassified items below /c.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.