mirror of
https://github.com/plankanban/planka.git
synced 2026-02-25 11:21:03 +03:00
No way to assign member(s) to a given task within a card #154
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @0x0fe on GitHub (Jan 16, 2022).
Hello,It seems there is no way to assign member(s) to a task.
Depending on how we use the kanban such feature is really necessary, otherwise there is not enough granularity level within the card.
Let me explain why i need it in my specific case, which may apply to others.
We design and produce electronic product (ODM), each list is a client (company), each card is a product. Since there is no way to add versions within a card there is one card per product revision. That way there is a very good overview at any time of the status of everything at a glance, which is the goal.
Each card (aka product) has several tasks which need to be assigned to different members.
If such feature planned to be implemented, if not i want to look at it but how should it be done?
@nickbe commented on GitHub (Mar 6, 2022):
Each card ID actually represent a task. So the "tasks" section within one card is just a list of subtasks and should be used as such. I I'm afraid the granularity level you want is exactly what Planka should not have. It should stay as simple as possible within a given set of features. We think that the current option to have control over different boards within a project is enough for lots of users.
I know there's always room to make a software more powerful and give it more and more features, but we are using Planka everyday because it does NOT have all those features. Especially in business environments 90% of the users reject software once it needs a manual to use it. If they begin to suspect that there are lots of features they still didn't find out about something inside them start to "give up".
I've seen it happen time and time again and we want to avoid that.
@GlitchWitch commented on GitHub (May 5, 2023):
@nickbe I do hope you'd reconsider this after all this time!
Being able to assign subtasks within a card to specific users is a relatively simple feature that has a lot of applicable business use cases and would surely be widely used by growing teams. The level of organisation this provides for specific work flows is huge.
I'd propose the following:
The same would go for due dates on subtasks.
These are such useful features that Trello feature-gates them behind a paid plan, knowing full well that companies will upgrade even just for those.
CC: @meltyshev
@meltyshev commented on GitHub (May 9, 2023):
Hey! Thank you for reaching out and explaining in detail. It's in our plans, but I don't have enough time to do many tasks at once 😔 It will most likely take some time, or someone will do PR.
@meltyshev commented on GitHub (May 12, 2025):
This should be resolved in v2, but feel free to reopen if the issue persists.