Feature Request — Tag-Based Filtering for Kanban Board

[flyflypeng]

🏷️ Issue Type

• 🐛 Bug Report
• ✨ Feature Request
• 📖 Documentation
• 🔧 Maintenance

📋 Summary

As a user, I want to be able to filter tasks displayed on a Kanban board by specific tags/labels within the Kanban configuration interface, so that I can focus on a subset of related tasks (e.g., all subtasks belonging to the same project) without switching between multiple boards or views.

🎯 Motivation / Problem Statement

When managing complex projects, I often break down a large task into 20+ subtasks and assign them all the same tag (e.g., #Project/X) for grouping and tracking purposes.

Current Pain Point:

• The existing Kanban board displays all tasks matching the current view/filters.
• There is no way to further narrow down the Kanban board to show only tasks with a specific tag.
• Users are forced to either:
  • Create a separate board/view for each project tag, or
  • Manually filter tasks each time, which is tedious and error-prone.

Desired Behavior:

• When using the built-in Timeline-based Kanban (or any Kanban template), I want to configure a tag filter at the board level so that the Kanban displays only tasks containing the specified tag.

💡 Proposed Solution

Add a tag/label filter option in the Kanban configuration panel that allows users to:

1. Select one or more tags from a pre-populated list of available tags.
2. Filter the Kanban board to display only tasks that match the selected tag(s).
3. Persist the filter configuration as part of the board settings (optional: save as a custom Kanban template).

👥 Who's affected?

• Project managers tracking multi-subtask projects
• Team leads who organize work by project tags
• Individual contributors who want focused, distraction-free Kanban views

[tu2-atmanand]

Hi @flyflypeng !

Thank you for sharing the ideas and also the suggestions!

Not sure, if I have completely understand this workflow, but it seems like filtering to have a custom filtered view. I also agree with you that, creating multiple boards can be a little cumbersome and it will be confusing, especially, when user is managing multiple projects in the same vault.

Upcoming features

I feel, your workflow needs some extra management features. And I believe, this will be possible with an upcoming change in this plugin. From the version 2.0.0 onwards this plugin will going to change its architecture for storing the user data. So, each of your board will be stored as a single .taskboard file inside your vault. And, as you know, one of the principles of this plugin is to have :
1 Board = 1 Project
So, I think, after the next major version, 2.0.0 has been released, you should be able to have more clarity on how you can manage your projects.

Please go through the following ticket, to learn more about this upcoming architectural change : #723 .

Current Workaround and some suggestions

For now, in the current version, 1.x.x, I think there are already few feature which you have suggested, which might help you to achieve some of your requirements. Let me explain these existing features so that you can get more idea on them

• Filter the Kanban board to display only tasks that match the selected tag(s).

This is already possible through the "Advanced Board Filters". You can access this filters from the top right corner button as shown in the below image :

Then you can enter the tag inside the filter and your board will only show you the tasks with that specific tag on them. As shown in the below image :

But, yes, you will have to create multiple boards for this, which is a little annoying and can become cumbersome to have multiple boards. You should be able to solve this issue, once we are in the version, 2.0.0. Because, then inside the same board, you can create multiple views and easily switch between those views to visualize the related tasks.

• Persist the filter configuration as part of the board settings (optional: save as a custom Kanban template).

At present, its possible to save the "Advanced Board Filters" for future use and to quickly load it. But its a little difficult and I am planning to make this UI/UX simpler in the future : #557

(Also, not that in the version, 2.0.0. Advanced Board Filters will be called as Advanced View Filters. Because inside each board file user will be able to create different views and each view will have its own individual filters, just like the core Bases plugin.)

Let me know your thoughts on this and if you have any other suggestions.

[tu2-atmanand]

Lets keep this ticket open until we release the version, 2.0.0, so that later we can see if your requirements are met in that version and if more enhancements are required in that version.

[flyflypeng]

Thank you very much for your detailed explanation. I didn't notice the "Advanced Board Filters" feature before, but now that I've used the "Advanced Board Filters" function, I've been able to resolve my issue.
However, from a user interaction and experience perspective, placing the "Advanced Board Filters" function directly in the Board configuration interface would be more appropriate.
I'm eagerly looking forward to the release of the 2.0.0 version.

[tu2-atmanand]

Also, forgot to share another main thing I wanted to share about the "Advanced Column Filters". This feature is usually not found easily by users, since its kind of hidden. But, the same power of "Advanced Filters" are also available to each column individually. Here is how you can access it :

• Click on the column count button to reveal the column menu :

• 

• Now click on the "Configure column filtering" option to open the Filtering settings for that column.

In the future, once we have improved the saving and loading of filters, it will be easier to select various filters to copy the filtering configuration easily.

[tu2-atmanand]

However, from a user interaction and experience perspective, placing the "Advanced Board Filters" function directly in the Board configuration interface would be more appropriate.

This is a nice suggestion. Initially, I felt like the current interface kind of looks similar to the bases. So I kept it similar to bases so users feel it easy to find the features. But will also think about this, after the version, 2.0.0 has been released.