It is currently not possible to collapse (recursively, for all child tasks) a given branch in Quire.
There is Shift-Left which closes all branches from a given depth and downwards. But it happens on all branches - not just the selected, the current branch.
Then one can right click the expand triangle (on web version) - and a promising popup menu with "Expand all subtasks" comes up. That part works - but after having expanded them - and clicking this triangle again - it still invites to Expand all subtasks. But they are already expanded then. (The correct thing would be to have the command Collape all subtasks).
Given that some nested subtasks can be open and others closed - it seems that the option to have (at the same time) both options Expand all subtasks and Collapse all subtasks there. (A nice tweak is to grey out Expand... if all subtasks actually are expanded.
Then - for those of us who prefer keyboard navigation - a keyboard shortcut would be nice (like Ctrl-Shift-Left to close recursively).
In some places it is noted that Alt-Left/Right should open / close recursively - but in my Linux Chrome it only jumps the cursor up / down the tree - no opening / closing happening there.
I hope you can test, debug and fine tune this. It matters in big note taking projects. Thanks !
Hi,
1 - That all branches on all levels rather frequently opens inadvertently is a bug of itself. It's not software behavior to ignore. (Compare to a car on a parking place - and when you're not there all doors open by themselves).
Do you log out of Quire often? When you log out, Quire won't remember your previously collapsed state. If you're staying logged in and still seeing tasks expand on their own, could you share the steps to reproduce it? That would help us look into it further.
2 - My suggestion: "Collapse all subtasks" is the logical complement of what you already have in the UI: "Expand all subtasks". It fits there in the UI.
Noted, and we'll share this with the team for review.
The workaround I suggested earlier came directly from our dev team, so they are aware of this. It's not a perfect solution, but it should help reduce the manual work.
Golda, Jun 4, 2026
Hi,
As I said - arrow, and "O" controls the open / close state of exactly one node (Yes, if it hides the child nodes, but when reopening the node again it is so that each of its child nodes retains whatever open / closed / state it had before).
I attach a screen recording of what I experience - with some comments.
Asteinarson, Mar 5, 2026
Hi,
Thank you for your feedback.
If you'd like to collapse or expand all subtasks under a selected parent task recursively, this can already be done by pressing:
- -> / <- to collapse or expand a group tasks by level
- O to expand/collapse the selected level
These actions apply to the currently selected branch.
Regarding the right-click option for Collapse all subtasks, thank you for the suggestion. I’ll pass this along to our team for consideration.
As for Alt + -> / <-, we currently don’t have that shortcut in Quire. Could you confirm if you might be referring to Shift + Left/Right instead?
If possible, could you also share a short screen recording of the behavior you’re experiencing? That would help us better understand and investigate the issue.
Golda, Mar 4, 2026
Hi,
Thank you for clarifying your feedback.
To collapse all subtasks, you can use the Expand up to 1st level option. This will collapse all deeper subtasks and keep only the first level visible. After that, you can collapse the root task to hide the remaining subtasks as well.
Golda, Mar 10, 2026
Update today - as I repeatedly stumble on this problem in the web version:
1 - That all branches on all levels rather frequently opens inadvertently is a bug of itself. It's not software behavior to ignore. (Compare to a car on a parking place - and when you're not there all doors open by themselves).
2 - My suggestion: "Collapse all subtasks" is the logical complement of what you already have in the UI: "Expand all subtasks". It fits there in the UI.
Your suggestion ("Expand up to 1st level") is a workaround (which still leaves a bit of manual work).
I am a paying customer. I think your role is to feed bugs and user experienced suggestions to the dev team.
Asteinarson, Jun 3, 2026