[ 
https://issues.apache.org/jira/browse/AIRFLOW-7048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074090#comment-17074090
 ] 

ASF subversion and git services commented on AIRFLOW-7048:
----------------------------------------------------------

Commit cc9b1bc78df1e82da37b885d2a8aaf5779c6209d in airflow's branch 
refs/heads/master from Ash Berlin-Taylor
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=cc9b1bc ]

[AIRFLOW-7048] Allow user to chose timezone to use in UI (#8046)

Co-authored-by: Sam Black <sambla...@users.noreply.github.com>

> Provide "timezone selection" mechanism in front-end
> ---------------------------------------------------
>
>                 Key: AIRFLOW-7048
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-7048
>             Project: Apache Airflow
>          Issue Type: Sub-task
>          Components: ui, webserver
>    Affects Versions: 1.10.0
>            Reporter: Ash Berlin-Taylor
>            Assignee: Ash Berlin-Taylor
>            Priority: Major
>              Labels: timezone
>             Fix For: 2.0.0
>
>
> Often users will want to see timezones in their "local" timezone (as defined 
> by browser), but there are useful cases when they would want to be able to 
> view times in other timezones.
> We should have "dropdown"/selection mechanism that lets the user choose:
> - Browser local (the default probably)
> - UTC
> - Ariflow server configured TZ (if it's not UTC)
> Possibly we should also have "DAG timezone" for any dag-specific page, when 
> that DAG is set to use a different TZ
> And then for flexability (and if it's not loads of work) let the user select 
> any arbitrary timezone ("America/New York", or "Europe/Paris" for instance) 
> from a list.
> The user's chosen TZ should be stored in a cookie (don't think it's necessary 
> to store this server side if all the translation is being done client side.)
> It might be useful to have a "quick toggle" between local and what ever other 
> setting is set.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to