[
https://issues.apache.org/jira/browse/AMBARI-13497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14966456#comment-14966456
]
Andrii Babiichuk commented on AMBARI-13497:
-------------------------------------------
+1 for the patch
> Ambari Web: Timezone issues
> ---------------------------
>
> Key: AMBARI-13497
> URL: https://issues.apache.org/jira/browse/AMBARI-13497
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.3
> Reporter: Oleg Nechiporenko
> Assignee: Oleg Nechiporenko
> Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13497.patch, timezone-issues.pptx,
> timezone-uid.tiff
>
>
> *BUG*
> 1. Open settings, change Timezone, save
> 2. Browser reloads. popup hdfs widget chart. Looks like it's using the right
> timezone
> 3. Close widget, then go and click on background ops. It's not using timezone
> for when a task is performed.
> 4. Close background ops. popup hdfs widget chart. Now it's back to the old
> timezone.
> 5. go to settings and you'll see your change is reverted.
> *BUG*
> 1. When saving timezone info, we should not be saving the property based on
> what is displayed in the UI.
> 2. See attached. This feels really fragile. There has to be some timezone
> guid that we can persist so that we are not dependent on what is shown to the
> user. This it important in case we change the display format/info and when we
> internationalize, we can't get stuck with this.
> *USABILITY*
> 1. On the graph, we should show the timezone we are displaying in. Users will
> want to know that now since it can change. See slide #1 in attached.
> 2. unrelated to timezone, we should also add Export text next to icon. Also
> in slide #1.
> 3. Since the Ambari Server timezone matters, we should let the user have this
> info as well on the settings dialog. See slide #2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
