Save user preferences #689
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
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)Project preferences:
The sort order of the form list(moved to #719)Whether managed or legacy QR codes are shown for app users(moved to #719)The text was updated successfully, but these errors were encountered: