Description
Search first
- I searched and no similar issues were found
What Happened?
When creating a new class tag in Logseq’s database version, the default parent is Root Tag
, meaning the tag does not inherit any properties from another class. Users can choose to keep Root Tag
as the parent or explicitly assign another tag (e.g. #Task
) to define inheritance. This is useful when modeling relationships such as having #Project
inherit status properties from #Task
.
However, once the parent has been changed from Root Tag
to another tag, it is no longer possible to revert it back:
- The interface shows the current inheritance chain (e.g.
Root Tag > Task
) directly under the tag title. - To change the parent, the user must click slightly to the right of the last tag in the "Parent" property row to open the tag selection popover.
- The dropdown includes both user-created and system-defined tags (like
#Task
,#Query
, etc.), butRoot Tag
is missing.
This means that if a user accidentally assigns a parent tag, there is no way to undo the change and return to Root Tag
— beside deleting and recreating the class tag entirely.
Reproduce the Bug
- Create a new class tag (e.g.
#Project
) in the database version of Logseq - Note that the default parent is
Root Tag
- Change the parent by clicking slightly to the right of the last tag in the “Parent” property row under the tag title (this could be described as the "Page properties" section, NOT "Tag properties")
- Choose any tag from the popover (e.g.
#Task
) - Attempt to revert the parent back to
Root Tag
by opening the same popover - Observe that
Root Tag
is not listed in the selection popover - The only way to restore
Root Tag
is to delete and recreate the tag from scratch
Expected Behavior
The parent tag selection popover should include Root Tag
as an option, allowing users to remove any assigned parent and restore the default inheritance state.
Files

CleanShot.2025-04-22.at.13.55.38.mp4
Browser, Desktop or Mobile Platform Information
OS: macOS Sequoia Version 15.3.2 (24D81)
Browser: Arc Browser Version 1.90.1 (61364), Chromium Engine 135.0.7049.85
(Should be reproducible in Chrome or any Chromium-based browser)
Logseq environments tested:
Additional Context
This limitation adds unnecessary friction when designing ontologies or adjusting class hierarchies in the database version. Since property inheritance is a core part of Logseq’s data modeling, it should be possible to flexibly switch between Root Tag
and other tags at any time. Including Root Tag
in the selection popover would significantly improve usability and reduce frustration from accidental changes.
Are you willing to submit a PR? If you know how to fix the bug.
- I'm willing to submit a PR (Thank you!)