-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relative date not updated on refresh unless underlying data changes #75729
Labels
bug
Fixes for quality problems that affect the customer experience
Feature:FieldFormatters
impact:low
Addressing this issue will have a low level of impact on the quality/strength of our product.
loe:small
Small Level of Effort
Team:DataDiscovery
Discover App Team (Document Explorer, Saved Search, Surrounding documents, Data, DataViews)
Comments
tsullivan
added
Feature:Filters
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
labels
Aug 25, 2020
Pinging @elastic/kibana-app (Team:KibanaApp) |
Nudge |
flash1293
added
Feature:Discover
Discover Application
and removed
Feature:Discover
Discover Application
labels
Sep 7, 2020
Hi, Can I please have an update on this. It's been a while and it looks like there's been no progress on this ticket. Must have been buried under other issues. Can someone please have a look. Thanks :) |
timroes
added
Feature:FieldFormatters
Team:AppArch
and removed
Feature:Filters
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
labels
Oct 13, 2020
Pinging @elastic/kibana-app-arch (Team:AppArch) |
Hi Guys - Just checking in on this. Any updates? Thanks |
Dosant
added
bug
Fixes for quality problems that affect the customer experience
impact:medium
Addressing this issue will have a medium level of impact on the quality/strength of our product.
loe:small
Small Level of Effort
triaged
loe:needs-research
This issue requires some research before it can be worked on or estimated
and removed
loe:small
Small Level of Effort
labels
Apr 19, 2021
exalate-issue-sync
bot
added
impact:low
Addressing this issue will have a low level of impact on the quality/strength of our product.
loe:small
Small Level of Effort
and removed
impact:medium
Addressing this issue will have a medium level of impact on the quality/strength of our product.
loe:needs-research
This issue requires some research before it can be worked on or estimated
labels
Jun 16, 2021
1 task
9 tasks
petrklapka
added
Team:DataDiscovery
Discover App Team (Document Explorer, Saved Search, Surrounding documents, Data, DataViews)
and removed
Team:AppServicesSv
labels
Dec 12, 2022
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Fixes for quality problems that affect the customer experience
Feature:FieldFormatters
impact:low
Addressing this issue will have a low level of impact on the quality/strength of our product.
loe:small
Small Level of Effort
Team:DataDiscovery
Discover App Team (Document Explorer, Saved Search, Surrounding documents, Data, DataViews)
Kibana version:
v7.7
Elasticsearch version:
v7.7
Server OS version:
Windows Server 2012
Browser version:
Chrome
Browser OS version:
Microsoft Edge Chromium 84.0.522.63
Chrome 84.0.4147.135
Original install method (e.g. download page, yum, from source, etc.):
Download page >> Installed as a service using the built-in PowerShell script
Describe the bug:
I have a CSV file that is updated weekly. It is then ingested by Logstash using its built-in file input plugin. One of the columns is "last seen", a timestamp that tells us when a particular record was last checked. The values of "last seen" are shown on a dashboard as a relative timestamp, ie "2 days ago". When the CSV file, and therefore the underlying data in the index, is updated the refresh button and the auto-refresh functionality nicely update the view to show the new relative timestamp. That is, if it's been recently updated, the value of "last seen" will update from "7 days ago" to "1 minute ago". However, if I leave this dashboard open for days, and the underlying CSV does not change, the value will keep showing "1 minute ago" even with auto refresh enabled and even if I manually click on the refresh button. As if the refresh function would have a built-in check for data changes that would say "nothing in the underlying data has changed, we're all good, I'm not going to refresh anything". This, of course, is wrong as relative date should always be relative to the actual timestamp and therefore it should be updated even if the underlying data shows the same values. The only way to regenerate these relative date fields is to reload the page completely using the refresh/reload button of the browser.
Steps to reproduce:
Expected behavior:
Relative date fields to be recalculated at every refresh, even if the underlying data has not changed.
Screenshots (if relevant):
The text was updated successfully, but these errors were encountered: