mirror of
https://github.com/plankanban/planka.git
synced 2025-12-06 09:13:16 +03:00
[Feature Request] View all currently assigned cards #627
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 @zensharp on GitHub.
Hi Planka community,
Could we get a screen which shows all cards assigned to the current user? This screen would show cards across all projects/boards. I'm thinking the user can access the screen by clicking an icon at the top right of the UI:
Trello and GitLab already have this feature. Here's what it looks like on Trello:
GitLab:
@nickbe commented on GitHub:
Something similar is already planned although different from trello.
@meltyshev commented on GitHub:
Hi! Thanks for working on this. If you forked the repository when it was still on version 1, that's likely why there's no Make Pull Request button - there have been significant changes in version 2. You'll likely need to re-fork the current version of the repository and manually migrate your changes. Some rework will be needed, as we've moved away from the container-based approach and now use selectors directly within components.
@joakimbaynaud commented on GitHub:
Hello, I created a fork of the Planka project and managed to create a page displaying all the current user's cards, but I don't know how to make the merge request. This is my first contribution to an open source project. Could someone explain how to do this?
@stanlystark commented on GitHub:
@meltyshev будет?
@GlitchWitch commented on GitHub:
@nickbe @meltyshev Is still planned? Any ETA?
@meltyshev commented on GitHub:
Yep, should be here: https://docs.planka.cloud/docs/development/set-up-environment.
By the way, I’ve reviewed the code a bit in https://github.com/joakimbaynaud/plankaV1, and it looks like you’re trying to load all the boards in order to get the assigned cards. This approach might work fine with just a few boards, but if you have hundreds or thousands, it will seriously impact performance. Because of that, it’s not suitable for production use in its current state.
I already have some ideas on how to improve this. First, we need to adapt the socket events to broadcast notifications per user rather than per board. We also need to decouple the Card component from relying on the current board selector and instead always use selectors by ID. This way, we can render cards independently of a board and ensure they are always up to date.
@joakimbaynaud commented on GitHub:
Did we have a tuto to lunch the app in dev mode, with npm, on the V2?