-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
【feature request for agenda 3】Adding an option to render tasks color according to defined tag colors in the all tasks view #303
Comments
Do you want to set a color for the entire task card? I'm afraid it's not quite appropriate. A task may have multiple tags, and having so many task cards would affect the visual effect. |
Currently, we can set the color for the specific tags as a filter, and we can only see the color when applying the filter |
Or put it like this: defining color at block level instead of page level |
Yeah, it would be really nice. I would tell you why in my specific use case: I divised three ways of doing it:
It would be nice if at least you could make it so the first tag that appears is the one used for the page colour system. Really thanks for you time in this project, it has already helped a lot 🫶 |
I think filters should also be able to achieve a similar effect as tags, for example, creating a filterA to query all tasks with tagA, then setting a color for this filter would suffice. You can refer to this document. https://www.notion.so/haydenut/English-fd47d1843e654f5485a07ef4935ed365#7bd975fe6d07453686a22d264c228f81 |
Ohhh yeah I have seen filter uses. |
This is a great plugin
The task assignment logic in 3.0 is amazing
One small change I desire is rendering tasks color according to their tags
One can only see the color when implementing a tag filter. However, In the all tasks view, the color is defined by page.
I'd like to know if you can implement an option to show the tag-defined color and the page defined color in the all-tasks view (when conflicting, using tag defined color).
The text was updated successfully, but these errors were encountered: