Persist view type of lists #2247

Open
opened 2 months ago by Bouni · 2 comments
Bouni commented 2 months ago

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
<!-- 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)
Collaborator
Related: https://github.com/go-vikunja/frontend/issues/70
dpschen added the
kind/bug
label 2 months ago
Owner

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?

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 Milestone
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: vikunja/frontend#2247
Loading…
There is no content yet.