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

Priority labels not shown in Kanban view #2285

New Issue
Closed
opened 2026-03-22 14:00:51 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-03-22 14:00:51 -05:00
Owner
Copy Link

Originally created by @Bouni on GitHub (Aug 21, 2025).

Description

We use priority labels on our tasks.
After updating to 1.0.0-rc1 the noe longer show up in the Kanban view.

Searching through the changelogs I fount this:

(labels) Show priority labels based on minimum priority setting (#3075)

After checking the setting it was set to medium. But even those with Priority high were not shown.
Changeing the setting to another value, save and then change it back did the trick.
Now the labels are shown again.

Maybe the upgrade process can trigger whatever the change on the UI does.

Vikunja Version

1.0.0-rc1

Browser and version

Firefox 142.0

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @Bouni on GitHub (Aug 21, 2025). ### Description We use priority labels on our tasks. After updating to 1.0.0-rc1 the noe longer show up in the Kanban view. Searching through the changelogs I fount this: ``` (labels) Show priority labels based on minimum priority setting (#3075) ``` After checking the setting it was set to medium. But even those with Priority high were not shown. Changeing the setting to another value, save and then change it back did the trick. Now the labels are shown again. Maybe the upgrade process can trigger whatever the change on the UI does. ### Vikunja Version 1.0.0-rc1 ### Browser and version Firefox 142.0 ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-03-22 14:00:52 -05:00
Author
Owner
Copy Link

@Bouni commented on GitHub (Aug 21, 2025):

I had a look at the sqlite db

All users have an empty frontend_settings column. After changing the setting and back for one user, it gets filled with something like this:

frontend_settings = {"allow_icon_changes":true,"color_schema":"auto","date_display":"relative","default_view":"kanban","minimum_priority":1,"play_sound_when_done":true,"quick_add_magic_mode":"vikunja"}

Maybe you should populate this with a sane default if empty

@Bouni commented on GitHub (Aug 21, 2025): I had a look at the sqlite db All users have an empty `frontend_settings` column. After changing the setting and back for one user, it gets filled with something like this: ``` frontend_settings = {"allow_icon_changes":true,"color_schema":"auto","date_display":"relative","default_view":"kanban","minimum_priority":1,"play_sound_when_done":true,"quick_add_magic_mode":"vikunja"} ``` Maybe you should populate this with a sane default if empty
GiteaMirror commented 2026-03-22 14:00:53 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Aug 31, 2025):

Fixed in 7510f8d4be, please check with the next unstable build (should be ready for deployment in ~30min, also on try).

@kolaente commented on GitHub (Aug 31, 2025): Fixed in https://github.com/go-vikunja/vikunja/commit/7510f8d4be4e16ab54ea359346fd9c2c6c58c4d9, please check with the next unstable build (should be ready for deployment in ~30min, also on [try](https://try.vikunja.io)).
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#2285
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?