github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-10 15:15:41 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

Show badge for blocked tasks #2099

New Issue
Open
opened 2026-03-22 13:55:48 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-03-22 13:55:48 -05:00
Owner
Copy Link

Originally created by @vikunja-bot on GitHub (Apr 1, 2025).

Original issue by UnsolvedCypher on 2021-04-15T01:09:42.000Z

It would be nice to have a badge for blocked tasks similar to the one for done tasks. It could also be useful to be able to filter blocked tasks (eg. hide blocked tasks from your to-do list since you can't actually do them yet).

Original issue on Gitea

@kolaente commented on 2021-04-15T06:44:04.000Z:

What do you mean by blocked tasks? Tasks that have a "blocked" relation with some other task?

danner26 commented on 2021-04-15T20:42:15.000Z:

I agree, the more I play with the app the more I find. Seems other have found similar quirks as I have

I think if a task is blocked by another task, then it should not show on the todo list. Maybe make this a configurable thing though. A simple toggle switch in the users settings for if they want blocked tasks to show, or not in the todo list.

UnsolvedCypher commented on 2021-04-15T21:29:57.000Z:

Yes I did mean tasks with a "blocked" relation 🙂

I think it could probably be a setting for the view to not show them in the list, or perhaps just have it as an option in the filtering. But I think the most important thing is to have a badge so you can at least see that the task is blocked.

@kolaente commented on 2021-04-15T21:50:14.000Z:

I see. I would consinder this an edge case and think it should at least not be a default for everyone. Also what should happen to other relation kinds, should they be visible as well? How to prevent the task views getting too crowded?

danner26 commented on 2021-04-15T22:15:06.000Z:

Good point. I think having small icons for specific relations would be very benificial to the UX. Often times if it is not directly shown in the UI, there will be a color difference between a "blocked" task and a "non-blocked" task (at least from my experience). I dont think all relations need a designation in the UI, but some I think do. You could do just an icon, or just a color, or both but either way I think it needs to be consistant across the whole UI.

Here is just an idea:

Relation Badge Color
Subtask image Light Blue
Blocking image Light Red

Obviously does not have to be the same icons, but just as an idea from what I have used in the past.

UnsolvedCypher commented on 2021-04-16T02:15:48.000Z:

I don't have a strong opinion on other types of relations. However, when a task is blocked, it means you usually aren't able to immediately attend to it, so I would argue that this relation is more important than others. If you want to see related tasks to a certain task you can just click on it, but I think it's necessary to be able to see if a task is able to be done just by looking at it without extra clicks.

Originally created by @vikunja-bot on GitHub (Apr 1, 2025). _Original issue by UnsolvedCypher on 2021-04-15T01:09:42.000Z_ It would be nice to have a badge for blocked tasks similar to the one for done tasks. It could also be useful to be able to filter blocked tasks (eg. hide blocked tasks from your to-do list since you can't actually do them yet). [Original issue on Gitea](https://kolaente.dev/vikunja/vikunja/issues/1778) --- _**@kolaente** commented on 2021-04-15T06:44:04.000Z_: What do you mean by blocked tasks? Tasks that have a "blocked" relation with some other task? --- _**danner26** commented on 2021-04-15T20:42:15.000Z_: I agree, the more I play with the app the more I find. Seems other have found similar quirks as I have I think if a task is blocked by another task, then it should not show on the todo list. Maybe make this a configurable thing though. A simple toggle switch in the users settings for if they want blocked tasks to show, or not in the todo list. --- _**UnsolvedCypher** commented on 2021-04-15T21:29:57.000Z_: Yes I did mean tasks with a "blocked" relation 🙂 I think it could probably be a setting for the view to not show them in the list, or perhaps just have it as an option in the filtering. But I think the most important thing is to have a badge so you can at least see that the task is blocked. --- _**@kolaente** commented on 2021-04-15T21:50:14.000Z_: I see. I would consinder this an edge case and think it should at least not be a default for everyone. Also what should happen to other relation kinds, should they be visible as well? How to prevent the task views getting too crowded? --- _**danner26** commented on 2021-04-15T22:15:06.000Z_: Good point. I think having small icons for specific relations would be very benificial to the UX. Often times if it is not directly shown in the UI, there will be a color difference between a "blocked" task and a "non-blocked" task (at least from my experience). I dont think all relations need a designation in the UI, but some I think do. You could do just an icon, or just a color, or both but either way I think it needs to be consistant across the whole UI. Here is just an idea: | Relation | Badge | Color | | -------- | -------- | ----- | | Subtask | ![image](/attachments/e9376ffa-f7cf-4fab-8309-5a4adb91e97f) | Light Blue | | Blocking | ![image](/attachments/2d29251b-da63-458b-aab1-55d6778027ed) | Light Red | Obviously does not have to be the same icons, but just as an idea from what I have used in the past. --- _**UnsolvedCypher** commented on 2021-04-16T02:15:48.000Z_: I don't have a strong opinion on other types of relations. However, when a task is blocked, it means you usually aren't able to immediately attend to it, so I would argue that this relation is more important than others. If you want to see related tasks to a certain task you can just click on it, but I think it's necessary to be able to see if a task is able to be done just by looking at it without extra clicks.
GiteaMirror commented 2026-03-22 13:55:49 -05:00
Author
Owner
Copy Link

@Elekam commented on GitHub (Jan 30, 2026):

Hello, I wanted to voice my support for this feature.

I have a significant amount of blocked tasks and clicking on a task just to discover/remember that it is blocked by something else would be great to avoid. These tasks also clutter the task list.

I was thinking of this just few weeks ago when that happened to me again, but also today when I read the 1.0 changelog and saw this.
I assume that is just a red label called "Blocked"?

A automatic visual indicator of the task being blocked like that would be great, but more important for me would be the ability to at least filter these tasks out.

I also wanted to say thank you for your work on Vikunja and the 1.0 Update, I am a happy user of it.

@Elekam commented on GitHub (Jan 30, 2026): Hello, I wanted to voice my support for this feature. I have a significant amount of blocked tasks and clicking on a task just to discover/remember that it is blocked by something else would be great to avoid. These tasks also clutter the task list. I was thinking of this just few weeks ago when that happened to me again, but also today when I read the 1.0 changelog and saw [this](https://vikunja.io/changelog/whats-new-in-vikunja-1.0.0/#comment-count-and-unread-tracking). I assume that is just a red label called "Blocked"? A automatic visual indicator of the task being blocked like that would be great, but more important for me would be the ability to at least filter these tasks out. I also wanted to say thank you for your work on Vikunja and the 1.0 Update, I am a happy user of it.
GiteaMirror commented 2026-03-22 13:55:49 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jan 30, 2026):

Thanks for the kind words!

The "Blocked" in the screenshot is just a label, that's correct. It does not really make sense that way but when I noticed I already spent 3 hours on the changelog post and just wanted to get it out.

If we go in the direction of indicating this, we'll also have to think about whether we should have indicators for the other relations as well. I think getting the ui right there is a little tricky (but totally doable)

@kolaente commented on GitHub (Jan 30, 2026): Thanks for the kind words! The "Blocked" in the screenshot is just a label, that's correct. It does not really make sense that way but when I noticed I already spent 3 hours on the changelog post and just wanted to get it out. If we go in the direction of indicating this, we'll also have to think about whether we should have indicators for the other relations as well. I think getting the ui right there is a little tricky (but totally doable)
GiteaMirror commented 2026-03-22 13:55:49 -05:00
Author
Owner
Copy Link

@Elekam commented on GitHub (Jan 30, 2026):

I could think of a few icons in my head that could be used for blocking, being blocked, being a parent task or being a child task etc.
Im not sure how easy it would be to make them or find publically available ones.

The other issue is a task potentially looking cluttered when it has a due date, subtasks, comments, a description and a few relations, with all the icons each of these things add to the task.
Maybe there could be a setting per project or user that decides whether specific relations should even be shown as an icon. Could also be extended to the other indicators like Description.

For example some users might only want to see the "Being blocked" icon, but dont care about icons for "Parent task", Subtask etc.

Another idea could also be to show the relations in the new task card preview. But thats another thing entirely.

I think being able to turn off specific icons might solve the clutter issue for people that would dislike it, I personally would rather have too much information visible at a glance than too little.

Of course desigining it in a way that it doesnt feel cluttered to most even if all icons are shown would be best but I have no idea how one would achieve that.
Im not a designer and I havent properly programmed for years so this is just a layman suggestions, I dont know how this would best fit into the code and design.

@Elekam commented on GitHub (Jan 30, 2026): I could think of a few icons in my head that could be used for blocking, being blocked, being a parent task or being a child task etc. Im not sure how easy it would be to make them or find publically available ones. The other issue is a task potentially looking cluttered when it has a due date, subtasks, comments, a description and a few relations, with all the icons each of these things add to the task. Maybe there could be a setting per project or user that decides whether specific relations should even be shown as an icon. Could also be extended to the other indicators like Description. For example some users might only want to see the "Being blocked" icon, but dont care about icons for "Parent task", Subtask etc. Another idea could also be to show the relations in the new task card preview. But thats another thing entirely. I think being able to turn off specific icons might solve the clutter issue for people that would dislike it, I personally would rather have too much information visible at a glance than too little. Of course desigining it in a way that it doesnt feel cluttered to most even if all icons are shown would be best but I have no idea how one would achieve that. Im not a designer and I havent properly programmed for years so this is just a layman suggestions, I dont know how this would best fit into the code and design.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#2099
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?