Optimization - consistent date formats #6385
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview > Optimization,
in the show_list views (
/optimization/show_list
and/optimization/show_list/123
), we convert iso dates to the user representation in JS.But, for saved report views (both in Optimization and in Reports), we use the formatted value provided by the API (
/api/results/20892?expand_value_format=true&hash_attribute=result_set
).Before, the show_list value was formatted as "07/22/2019 9:44:50 am", in browser-local timezone.
Now, the show_list value is formatted as "07/22/2019 09:44:50 UTC", in the timezone set in user settings.
This also exposes the current user timezone (
session[:user_tz]
) to JS (ManageIQ.timezone
), in theEurope/London
/Etc/UTC
... format.Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1769333