-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Description
In my understanding, roughly, one project equates to one code base or to one repo. If you work with multiple repos, the amount of project cards gets a bit busy and without clicking into each individual project card, you don't really know what's going on there in terms of tasks. You might have forgotten what is there in the first place, But nevertheless tasks are still there in different states. My suggestion is to add to the project card three most important category of tasks, specifically numbers of those tasks. category could be represented by a corresponding colour already used in the kanban . In my opinion, the most important categories are to do, in progress, In review. What's done cancelled probably is not so important as to be on the card. In any case, this is just a suggestion and there could be plenty of other ways of representing it.
The idea is to have a very high level stats of which projects I need to look at in depth and which ones could be left alone for now.
Thanks
