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

Persist view type of lists #420

New Issue
Open
opened 2025-11-01 20:55:59 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-01 20:55:59 -05:00
Owner
Copy Link

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

Original issue by Bouni on 2022-08-11T12:21:01.000Z

Version information:

Frontend Version: 0.19.0
API Version: v0.19.0
Browser and OS Version: Firefox 103.0.2 | Windows 10 Pro

Steps to reproduce:

  1. Select Kanban as view type for a list
  2. Logout
  3. Log back in

Expected behavior:

When selecting Kanban as vie type for a list, that setting should be persisted (per user so that everyone can have their desired view type)

Actual behavior:

After loging back in the view type is back to list instead of kanban

Checklist:

  • I have provided all required information
  • I am using the latest release or the latest unstable build
  • I was able to reproduce the bug on try

Original issue on Gitea

dpschen commented on 2022-08-11T17:20:41.000Z:

Related: https://github.com/go-vikunja/frontend/issues/70

@kolaente commented on 2022-08-12T07:01:04.000Z:

The problem is this is a setting which should be saved per user. If someone else logs in using the same browser the old view the user before used is selected. To fix this properly we'd need to save this into the api I think?

Originally created by @vikunja-bot on GitHub (Apr 1, 2025). _Original issue by Bouni on 2022-08-11T12:21:01.000Z_ <!-- Please fill out this issue template to report a bug. If you want to propose a new feature, please open a discussion thread in the forum: https://community.vikunja.io --> **Version information:** Frontend Version: 0.19.0 API Version: v0.19.0 Browser and OS Version: Firefox 103.0.2 | Windows 10 Pro **Steps to reproduce:** <!-- Add clear steps to reproduce the bug. Provide screenshots where applicable. --> 1. Select Kanban as view type for a list 2. Logout 3. Log back in **Expected behavior:** <!-- Describe what happened. --> When selecting Kanban as vie type for a list, that setting should be persisted (per user so that everyone can have their desired view type) **Actual behavior:** <!-- Describe what happened instead. --> After loging back in the view type is back to **list** instead of **kanban** **Checklist:** * [x] I have provided all required information * [x] I am using the latest release or the latest unstable build * [x] I was able to reproduce the bug on [try](https://try.vikunja.io) [Original issue on Gitea](https://kolaente.dev/vikunja/vikunja/issues/1969) --- _**dpschen** commented on 2022-08-11T17:20:41.000Z_: Related: https://github.com/go-vikunja/frontend/issues/70 --- _**@kolaente** commented on 2022-08-12T07:01:04.000Z_: The problem is this is a setting which should be saved per user. If someone else logs in using the same browser the old view the user before used is selected. To fix this properly we'd need to save this into the api I think?
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#420
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?