-
Notifications
You must be signed in to change notification settings - Fork 282
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What am I doing? Across boards? #1630
Comments
Like a filter e.g. #1507 ? |
Well, yes, it is like a filter, but, I guess it employs two filters:
Then, add a column at the dashboard/startpage and show for each board the top card's name. Required would be
|
Would this solution be helpful? |
#1319 seems quite helpful. I would argue that not everybody is using due dates (I simply do not need these in my project management). But the #1319 (comment) suggestion comes close to what I would really like to see - with the difference that I was not looking for the filter by due dates but a filter of what is currently worked on (in the kanban logic the "doing" cards (all of them, or simply the top "doing" card). |
Just to add an example. I work on these projects/boards (with cards) in each board I mark a card with a tag or with a stack* as currently worked on. Now an overview of all those marked cards would be helpful: list of * |
The main issue i see with this is that we currently have no way to define which column is the todo one and this is rather specific to your use case. I think a general approach of a card overview with upcoming/important ones is more the way to go as aimed for in #1319. |
When I approach the deck app, at first I see a list of my boards (with the owner), for my different projects.
I wonder: could we add a column? For instance a column of list cards of "doing" decks.
that would allow me to see at one glance where I am across various projects.
Or, specifically: for each board, one deck could be optionally&manually marked as "show on overview page"; and then the first/top card of that deck is shown on the overview page.
The text was updated successfully, but these errors were encountered: