Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Save user preferences #689

Open
matthew-white opened this issue Feb 8, 2023 · 1 comment
Open

Save user preferences #689

matthew-white opened this issue Feb 8, 2023 · 1 comment
Assignees
Labels
backend Requires a change to the API server enhancement New feature or behavior frontend Requires a change to the UI needs testing Needs manual testing

Comments

@matthew-white
Copy link
Member

matthew-white commented Feb 8, 2023

The user can make a number of selections/choices in Frontend that we've talked about persisting. We've talked about persisting them server-side. Some preferences seem to be top-level/sitewide, while others seem per-project. We already have sitewide settings (for usage reporting), project settings, and form settings. However, those are not specific to the user. This issue is about saving individual users' preferences.

Top-level/sitewide preferences to persist:

  • Whether the top panel on the homepage is shown or not (moved to #719)
  • The sort order of the project list

Project preferences:

@matthew-white
Copy link
Member Author

I've updated the description of the issue to make it clear that @brontolosone's work will close this issue. This issue is about adding a framework for saving user preferences, then using that framework for a couple of specific preferences. There are other user preferences that we want to save, and I've moved those to a separate issue (#719).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Requires a change to the API server enhancement New feature or behavior frontend Requires a change to the UI needs testing Needs manual testing
Projects
Status: ✏️ in progress
Development

No branches or pull requests

2 participants