Hi. Been using Vikunja for about a month. I am self hosting with the latest stable docker image. I use the UI only, as my CLI experience is fairly lacking. Really liking it and am content managing around the few bugs I have found. That said, I don’t know if this is a bug, or if it is ultimately a feature request. But…
What if I don’t want team-members to see the whole project? Just a task from a number of different projects…
Currently I have to “show” them the whole project so they can see their singular item in it, which they have to search for, find, or filter themselves. And more than that, If I want them to be able to edit the ONE task they are assigned to they have to be given access to write privileges to all the other tasks in the project because thats the only place it appears those privileges exist.
This cant be as intended. Am I missing something? I mean I miss things… a lot.
As far as I can tell, this is currently as it is designed. A task if part of a project, if you want a member to work with this, they need permissions on the project. It’s that easy (and therefore not very flexible) at the moment.
There are thoughts to put in a more fine grained permission system, not sure if that use case would be covered and if that would be available for everyone: Vikunja as a business
I mean… if I have a project and different people need to do different tasks and do not need (or even more so should not be allowed) to see others tasks and parts of a project… It’s sort of limiting for what I would think is little reason.
And beyond that, having to open up the project en mass so they can comment on their tasks is a security risk given their ability to mess with areas they don’t have any business in. And beyond that, having them not only be able to check the box that a task is done, but allowing them to delete the task all together, and with that deleting the admins copy of that task without notification or simple recovery… well, it makes the system seem sort of like an assignment system in name only.
The only resource you would have is to create separate projects for each member, share only that project with that member, and then duplicate the tasks in your admin account so you have a record of what you assigned in case they corrupt or delete it in some way… This seems pretty silly when you could just assign tasks (in general from anywhere) specifically to anyone in your team, and only allow them to check done or comment…
Thats what seems pretty straight forward, not the current iteration. Just my thoughts. not trying to be argumentative, but it seems to clear work to miss the mark of how something like this would be used, and is used in comparable applications.
I get your point, and I’m not saying that it’s a bad idea - I’m merely saying that this is currently not supported in Vikunja, to the best of my (just another user!) knowledge.
It really depends on your use case - we’re using Vikunja within an organization having 400+ members and the current structure works fine for us. Which is already more than impressive, given that Vikunja claims to be a todo app and doesn’t intend to be an alternative to full fledged project management tools which - no offense - might be closer to your use case.
So with 400 people, tasks don’t go missing or get changed? How would you know if it did? I mean, regardless of scope, one seems easier to implement and considerably more user friendly in any instance. You have 400 employees who have to sort through the organization of others design, to find the ones that are yours specifically, or each one, all 400, have to make (or have a boss make) separate filters to find them… No matter what the scope, finding the tasks you have been assigned without what could be countless others and not being able to flub things up in 399 other peoples lists seems like a no brainer. I would think the more hands int he pot the more obvious this got, not less.
Again, I don’t want to argue. Your use case might be as valid as ours and our mindset might simply be different. Apparently you’re coming from a corporate environment (talking about employees, boss has to do something, …), so you might actually be a perfect fit from a target audience perspective for the proposed features in the thread I linked above.
To answer your question: We’re not a corporate environment, we’re a non-profit organisation, and no, tasks don’t go missing. Tasks don’t get messed around with even in projects where all 450+ members have write access to. If someone wanted to mess with us they could, and if there were more advanced settings we might use them very selectively, but the combination of Single Sign On (OIDC), automatic team member assignment based on OIDC roles and permissions on group level work just fine for us.
Regardless, the current status is: it’s not supported, if you want it, you can either contribute yourself, create the code and docs and a merge request against the project (although I highly recommend describing a potential implementation first and seek approval from the author) or propose a feature request as mentioned in your initial post.
2 Likes