Open mwakerman opened 5 years ago
Does this feature make sense? I would say, that there should be a board per project that can be opened. Not a list in a board per project.
Example: I have 5 main projects. For each main project I have multiple sub- and sub-sub-... projects.
My understanding of a kanban board is, that you can move a card from one list to another. Now, if you define a list as project, you would move tasks between projects...
Am I wrong?
I find your approach to have lists that represent labels good.
Hi @fschirinzi - you are correct. I personally don't think projects-as-lists is very "Kanban" which is meant to show the state of a task (which changes) rather than it's project (which should be relatively static). However, some people don't have Todoist Premium so they don't have labels and are using projects to fulfil this need (note that you can still actually use labels in the Todoist API without premium, they are just blocked in the apps).
Anyway, I get 1-2 requests a week for this feature so I've added it here :)
I'm a new user but this was the first thing that struck me.
How about multiple boards that could be selected and configured on a per project basis rather than projects in the main board? This may require an alternative login method in the future rather than linking the API so to allow settings to move between different machines/browsers.
+1
@finnwood
How about multiple boards that could be selected and configured on a per project basis rather than projects in the main board?
This is already possible. When you apply a filter to your board the details of this filter are also stored in the URL which allows a specific board to be bookmarked. Bookmarks solve multiple problems. Firstly, they are easy to sync between browsers and most people already do use a browser that allows for easy and secure syncing. And most importantly, it's not clear where the configuration of these boards could be "saved". Kanbanist is proudly serverless and talks directly to the Todoist API which solves about 99% of any privacy or security concerns one may have in providing their API token. The code is also open source so people can see exactly how their data is treated. This is kind of unrelated to the actual issue though...
I understand that people want to be able to see all their projects in lists on a single board. I also use Trello and I often treat individual lists as projects where I never move a task from one list to another (but I do often reorder them in a list). But Kanban is a methodology about moving tasks between their states rather than between projects. A task doesn't change "project" when it goes from Todo → In Progress.
@mwakerman
I didnt realise that this information was stored in the URL. I must try that as I already use a similar method with specific shortcuts for todoist.
+1 vote for board per project instead of labels.
@mwakerman Given that todoist removed support for free users to do label management through the API last month, it seems like there will be even more requests for this kind of project-as-list feature. I understand that it isn't very "kanban" to show lists of projects though, so maybe support for this is out of scope.
I think if I had this feature I would probably use it to create categorized backlogs. It would be nice to see multiple projects listed out on the left side of my board, and drag from multiple different lists. I like to see which tasks I have left to do from both my work and individual lists. It could also be nice to list out all the books I have left to read or place I want to travel. It will also give free users the chance to use some of the kanbanist list features without needing to involve labels.
There are a bunch of small decisions to make to know a good way to implement this. Regardless, is this a feature that the community is currently working on or would be interested in beginning work on? I would like to contribute
@michaeldboyd thanks for the message, it's not something I'd thought about since the premium lockdown of labels API and I think it probably does change the calculus.
The things I'm currently thinking about:
I'd love a hand with implementing this. I'll aim to scope the work this week and update this issue with the pieces and approach.
Wondeful! Forgive me for spitballing a bit bigger scope than we might be prepared to handle, but here are some thoughts.
Project based approach In the first iteration it would be easier to implement a purely project list based configuration and then offer the option to switch to the original label-based configs for pro users.
If we did a 100% project list based board, the labels could then be used as tags on each task, or to create swimlanes.
Hybrid approach Alternatively, I had also been thinking that a user could have project based lists and label based lists side by side. This will definitely be a little confusing to use. What happens when tasks switch state?
However, the meaning of project vs label might get blurred. We could clear this up by separating the "projects" from the "progress" board (for example, all the projects lists are on the left, then a kanban board is on the right). I can drag my tasks from individual projects into the 'new', 'doing', and 'done' columns. - This gives free users the chance to hack together a kanban board without removing any existing functionality.
Easily the most common feature request is to have lists represent Todoist projects (rather than labels).