Add ability to configure default project view #2153

New Issue

waza-ari · 2024-03-02T17:51:08Z

waza-ari commented

2024-03-02 17:51:08 +00:00

Description

The default project view is currently hardcoded in the frontend to be project.list. I'd like to propose an additional configuration option to make this configurable. That is, if there's no preference stored by the user (in the localStorage), this value is used instead of the hardcoded default.

PR to add this feature will follow shortly. Please note I have no experience with Go and nearly no experience with Vue, so please check the proposal carefully :)

Sorry, cannot change the tag myself :(

Vikunja Version

unstable

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

### Description The default project view is currently hardcoded in the frontend to be `project.list`. I'd like to propose an additional configuration option to make this configurable. That is, if there's no preference stored by the user (in the localStorage), this value is used instead of the hardcoded default. PR to add this feature will follow shortly. Please note I have no experience with Go and nearly no experience with Vue, so please check the proposal carefully :) Sorry, cannot change the tag myself :( ### Vikunja Version unstable ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_

👍 1

waza-ari added the

kind/bug

label 2024-03-02 17:51:08 +00:00

waza-ari referenced a pull request that will close this issue

2024-03-02 17:51:23 +00:00

feat: add config flag to configure default project view #2154

konrad added

kind/feature

and removed

kind/bug

labels 2024-03-03 21:37:59 +00:00

konrad commented

2024-03-03 21:41:43 +00:00

Quoting myself from #2154:

The way views work will fundamentally change in the next release, which will essentially require a rewrite of the whole thing as you implemented it now (and you couldn't have known this, I guess that's on me). Given how small your implementation is, I'd rather reimplement this instead of merging it now and then reworking it once that change lands.

I think this should be a per-user or per-project setting, not globally defined.

Let's take a step back and discuss this further in the issue you opened about this.

Views will be a lot more configurable in the upcoming release, moving away from the current structure. Because of this, there might be more than one (or only one of) list/gantt/table/kanban view per project, not only one. This has a few implications:

Which view should be shown when the configured default view is not available in the project?
Which view should be shown when there is more than one of the user's configured?

The more I think about it, the best way to solve this is either

Always show the "first" view, let users configure in the project settings which one is "first"
Add a setting in the project to configure the default view per project

Quoting myself from #2154: > 1. The way views work will fundamentally change in the next release, which will essentially require a rewrite of the whole thing as you implemented it now (and you couldn't have known this, I guess that's on me). Given how small your implementation is, I'd rather reimplement this instead of merging it now and then reworking it once that change lands. > 2. I think this should be a per-user or per-project setting, not globally defined. > > Let's take a step back and discuss this further in the issue you opened about this. Views will be a lot more configurable in the upcoming release, moving away from the current structure. Because of this, there might be more than one (or only one of) list/gantt/table/kanban view per project, not only one. This has a few implications: * Which view should be shown when the configured default view is not available in the project? * Which view should be shown when there is more than one of the user's configured? The more I think about it, the best way to solve this is either 1. Always show the "first" view, let users configure in the project settings which one is "first" 2. Add a setting in the project to configure the default view per project

👍 1

waza-ari commented

2024-03-04 13:46:26 +00:00

Okay that makes a lot of sense. The first option you mentioned there (make it configurable on a per project level). Imho it should still allow the user to make their choice (among the available choices that might be limited by the project)

If that is planned anyway we can probably close this issue for now.

Okay that makes a lot of sense. The first option you mentioned there (make it configurable on a per project level). Imho it should still allow the user to make their choice (among the available choices that might be limited by the project) If that is planned anyway we can probably close this issue for now.

👍 1

konrad commented

2024-03-04 14:48:30 +00:00

It's somewhat planned on a project level (as the "first" view), but we could keep this issue open to allow configuration on a per-user level.

Sign in to join this conversation.