getredash/redash
View on GitHubUser configuration for date/time format & default timezone
Open
#618 opened on Oct 20, 2015
18 comments (18 comments)10 reactions (10 reactions)0 assignees (0 assignees)Python24,845 stars (24,845 stars)4,236 forks (4,236 forks)batch import
help wanted
Description
See #617 and #411 for more details.
Contributor guide
- Tech stack
- python
- Domain
- backend
- Issue type
- feature
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 3
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- 3-5 days
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- stale
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- needs investigation
- Prerequisites
- PythonFlaskDatabase migrationsUser settings
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 35
- Research direction
- First, review issues #617 and #411 for detailed requirements. Examine the user model (likely in redash/models/user.py) and the API endpoints for user settings (e.g., redash/api/settings.py). Understand current date/time handling in both backend and frontend. Propose a solution to add configurable date/time format and timezone fields to the user profile, update the API to return and accept these settings, and ensure they are applied consistently across the application.