I’m using Vicu with a deeply nested Vikunja project structure (projects - subprojects - sub‑sub‑projects). Vikunja itself supports arbitrary nesting and shows the full hierarchy in its UI.
In Vicu, the project view only treats direct child projects (one level down) as sections. Grandchild projects (sub‑sub‑projects) do not appear as sections, which makes it hard to work with multi‑level project hierarchies in a single view.
I’d really love an option for sections to support 2+ levels of nesting.
Current behavior
All top-level-projects are visible in the sidebar (so the full hierarchy from Vikunja is synced correctly).
When I open a project that has subprojects, those direct children are rendered as sections in the main project view.
If a subproject itself has child projects (sub‑sub‑projects), those grandchildren do not appear as additional sections under the parent project view.
In other words, the “subprojects as sections” feature stops at one level deep.
Desired behavior
One of the following (any of these would solve the workflow problem):
- Recursive sections option
- Allow sections to include not only direct child projects but also grandchildren (and possibly deeper) of the current project.
- This could be a setting, e.g. “Show nested subprojects as sections (depth N)” where N is configurable or at least 2.
Thank you!
I’m using Vicu with a deeply nested Vikunja project structure (projects - subprojects - sub‑sub‑projects). Vikunja itself supports arbitrary nesting and shows the full hierarchy in its UI.
In Vicu, the project view only treats direct child projects (one level down) as sections. Grandchild projects (sub‑sub‑projects) do not appear as sections, which makes it hard to work with multi‑level project hierarchies in a single view.
I’d really love an option for sections to support 2+ levels of nesting.
Current behavior
All top-level-projects are visible in the sidebar (so the full hierarchy from Vikunja is synced correctly).
When I open a project that has subprojects, those direct children are rendered as sections in the main project view.
If a subproject itself has child projects (sub‑sub‑projects), those grandchildren do not appear as additional sections under the parent project view.
In other words, the “subprojects as sections” feature stops at one level deep.
Desired behavior
One of the following (any of these would solve the workflow problem):
Thank you!