Currently i can only view tasks for sub projects by clicking on each one, is there a way to show all tasks from sub projects just by clicking on the parent project?
Create project “test parent project”
Create task “test parent project task”
Create new project “test parent project sub project” with parent of “test parent project”
Create task “test parent project sub project task”
View kanban of “test parent project”
That could be a temporary solution - but how would the filter look?
I created projects “parent”, “parent_sub1”, parent_sub2" and tried “project like parent%” in the filter, but “project” appears to translate to the project_id, not to the title.
And I have not found a way to retrieve project_id of a project other than to check in the database itself.
I started using Vikunja a few days ago and I find it amazing!
This feature is probably the one I miss the most.
I work as a team leader in a small team of just 2–3 developers. Each project is divided into one or more sub-projects (e.g. a CRM composed of Features, Tickets, Bugs, etc.).
I would really appreciate a global view starting from the main project, as it would help allocate resources more effectively.
Throwing my vote in for this one as well - I realise it’s quite old, but it would be great to be able to see a gannt chart of all sub projects.
Am aware I can use saved filter and individually list project names, but would be better if I could either just click the top project or create a dynamic filter “child of project xyz” etc.
In an ideal world, the gannt chart would show me 2 views (selectable) - Details for all tasks in all child projects or just the high level earliest date <> latest date for all tasks of a child project.
Request #2272 seems to have been the most active and to be the closest to being merged, but activity on it seems to have stalled a couple of months ago, sadly. I don’t think there’s anything I can do myself to help one of these get over the line, as I have no development experience.
I forked the project some weeks ago as the app is quite good compared to other paid options I was using before, like Todoist and Skedpal.
I did an implementation of this feature myself and wanted to share in case it could be useful. It does not look like the ones in the Pull Requests 2272 and 2592 though.
Unfortunately it also seems to have got stuck with only one test being failed (a minor one by the looks of it, though what do I know) and no activity for several weeks.
A while back I manually merged the code of PR 2272 into Vikunja v2.3 and compiled it locally, and that’s what I’ve been running since, instead of using a Docker image. It works perfectly. However it was a lot of work as a non-specialist to figure out how to do that, and it’s preventing me from upgrading - I don’t really want to do all that over again each time there’s a new Vikunja version. I might do it soon though with this new PR and v2.5, to get access to the new API version.
No complaints from me, by the way - I know nobody is getting paid for this and I’m very appreciative of what people have done!
I had made it work with a manual workaround when discussing with @kolaente how Vikunja could improve the logic of projects/sub-project/tasks/subtasks to make it more consistent and functional (which would as a result resolve the feature request here). I think the project would greatly benefit from this approach as it would address many other requests and use cases.
